----- Original Message ----- > From: "Junio C Hamano" <gitster@xxxxxxxxx> > To: "Conrad Irwin" <conrad.irwin@xxxxxxxxx> > Sent: Wednesday, August 17, 2011 2:41:41 PM > Subject: Re: [PATCH] Disallow creating ambiguous branch names by default > > We should be giving these warning messages immediately after creating > potentially problematic refs, i.e. just after "git branch v1.0.0" and > "git checkout -b v1.0.0". The user experience should look like this > instead: > > $ git branch v1.0.0 > warning: refname 'v1.0.0' is ambiguous. > advice: you may want to rename it to an unambigous name with > advice: git branch -m v1.0.0 v1.0.0-branch > $ git branch -m v1.0.0 v1.0.0-branch ;# thanks for an advice > > $ git checkout -b v1.0.0 > warning: refname 'v1.0.0' is ambiguous. > advice: you may want to rename it to an unambigous name with > advice: git branch -m v1.0.0-branch-2 > $ git branch -m v1.0.0-branch-2 ;# thanks for an advice Should case insensitive matches be added to the tests? This morning I discovered coworkers working on branches foo and Foo thinking they were on the same branch... Rather trivial to clean up, but certainly caused some confusion in the office. Thanks, Stephen -- 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