Re: Branch Name Case Sensitivity

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/28/2014 10:11 AM, Stephen Leake wrote:
> Karsten Blees <karsten.blees@xxxxxxxxx> 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@xxxxxxxxxxxx
http://softwareswirl.blogspot.com/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]