Brandon Casey, Thu, Jun 07, 2007 00:13:48 +0200: > > When a branch and tag have the same name, a git-checkout using that name > succeeds (exits zero without complaining), switches to the _branch_, but > updates the working directory contents to that specified by the _tag_. > git-status show modified files. Bad. To reproduce: mkdir a && cd a && git init && :> a && git add . && git commit -m1 && :>b && git add . && git commit -m2 && git tag master HEAD^ && find .git/refs/ && gco -b new && gco master && git status > Looks like the ambiguity issue was brought up last year, and git is now > *supposed* to warn when it encounters an ambiguous name. I agree with > Petr, it should fail violently, preferably as Josef Weidendorfer > suggests also printing out the ambiguous matches so the user can cut and > paste. > That'd be failing friendly :) Very good idea - 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
