On Thu, Aug 18, 2011 at 6:53 AM, Stephen Bash <bash@xxxxxxxxxxx> wrote: > > 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. > I can certainly see the use-case, but there's definitely a step-change between "this branch has the same name as something else", and "this branch is going to confuse you". When trying to change the code to be a warning as Junio suggested, I did think about expanding the definition of ambiguous to include things that are merely confusing; however it's not clear where to stop (i.e. should we warn about <remotename>/<anything>, foo and f00, a branch called " " [the non-breaking space]). There's probably an argument for more general warning, but I don't think I understand when it should be shown well-enough. Conrad -- 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