On Nov 19, 4:55 pm, "Michael P. Soulier" <msoul...@digitaltorque.ca>
> On 18/11/09 Jeenu said:
> > Hi,
> > If I've two branches a.b.c and a.b.c.d, why does 'git checkout'
> > complains about ambiguous refnames? For example, if I'm in a.b.c.d,
> > 896 $ git checkout a.b.c
> > warning: refname 'a.b.c' is ambiguous.
> > Switched to branch "a.b.c"
> > Is this some kind of a side effect of commit abbreviation? If so is
> > this kind of branch naming considered unsafe? Is there a way to make
> > git accept ref names verbatim, even if there's potential operation
> > that'd fail because of ambiguity?
> I'd have to dig further, but first are you sure that you don't have any tags
> or other references called a.b.c?

Well, 'git branch -a' shows only a.b.c and a.b.c.d; and 'git tag -l'
shows nothing. If there's no other command I should be trying, yes,
there is no other reference to a.b.c.



You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to