On 02/06/2012 06:06 AM, Jeff King wrote: > I kind of agree that we shouldn't be unnecessarily restrictive. On the > other hand, I am stretching to find the plausible reason that one would > want to throw away the normal convention. Code aside, it simply > introduces a slight communication barrier when talking with other git > users, and for that reason should be something you don't do lightly. I > don't recall seeing anybody complain seriously about it in the past six > years of git's existence. In the real-world situation when I noticed this bug, I wasn't trying to use a nonstandard name for "master". What I was doing is importing a snapshot of some code from another non-git project onto a "vendor branch", which I knew I would later want to merge into my own work (which I planned to do on master). 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