Michael Haggerty <mhagger@xxxxxxxxxxxx> writes: > On 11/22/2011 06:49 PM, Junio C Hamano wrote: >> Michael Haggerty <mhagger@xxxxxxxxxxxx> writes: >>> Currently git handles references names case-sensitively and allows >>> multiple reference names that differ only in case. >> >> We do the same for in-tree paths, by the way. Ultimately, I think the >> sane thing to do is to appeal to the user's common sense. [...common >> sense aka "if it hurts don't do it" omitted...] >> >> I think refnames have exactly the same issue. In theory, you could have >> "Master" and "master" branches, and nothing stops you from trying to do >> so, but in practice, if it is not useful for you and your project, and >> if it is equally fine to use some other name instead of "Master" for the >> purpose of you and your project, then there is no strong reason for doing >> so, unless you are trying to irritate users on case folding platforms. > > I agree. > > But git could nevertheless help users (1) by providing config settings > or hook scripts or something that could be configured in a repository to > prevent case-conflicts from entering the project history; (2) by > emitting an error when such a conflict arises rather than getting so > confused. Yeah, and you didn't have to say "But"; we are in agreement (see my other message in response to the same message from you). -- 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