Re: Branch Name Case Sensitivity
- From
Michael Haggerty <mhagger@alum.mit.edu>
- Date
- Feb 28, 2014, 09:49 UTC
- Message-ID
- <53105BC0.5040304@alum.mit.edu>
- In-Reply-To
- <8538j31u1n.fsf@stephe-leake.org>
On 02/28/2014 10:11 AM, Stephen Leake wrote:
Show 7 quoted lines
> Karsten Blees <karsten.blees@gmail.com> writes: > >> If I understand the issue correctly, the problem is that packed-refs >> are always case-sensitive, even if core.ignorecase=true. > > Perhaps that could be changed? if core.ignorecase=true, packed-refs > should be compared with case-insensitive string compares.
I think you are putting too much focus on what the local Git repository does. As soon as you pull content from somebody else, you are at the mercy of the reference names that they have chosen.
In my opinion, a more fruitful approach is to have a pre-receive hook at your central repository that prevents references that differ in case only from being pushed in the first place. As an extra convenience, you can set your local repos up with a pre-commit hook that does the same thing, so that developers (usually) see the problem immediately rather than only when they try to push.
Of course, the pre-receive/pre-commit hooks could be even stricter by, for example, allowing only lower-case branch names.
Michael
-- Michael Haggerty mhagger@alum.mit.edu http://softwareswirl.blogspot.com/