From: Duy Nguyen Date: Fri, 06 Jun 2014 01:37:55 GMT Subject: Re: [PATCH v3] receive-pack: optionally deny case clone refs Message-ID: In-Reply-To: <1402015954-5320-1-git-send-email-dturner@twitter.com> On Fri, Jun 6, 2014 at 7:52 AM, David Turner wrote: > Create the option receive.denycaseclonerefs, which checks pushed > refs to ensure that they are not case clones of an existing > ref. This setting is turned on by default if core.ignorecase is > set, but not otherwise. Just thinking out loud as I haven't had time to read this patch carefully, but I wonder if there's a potential performance problem with ref_is_denied_case_clone(). What if the receiver repo has 60k refs? Should we use name-hash (or a variant of it)? What if the sender pushes 60k refs in one go, will ref_is_denied_case_clone check against existing refs only, or it will cover more and more refs from the 60k input? -- Duy