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? Mike -- Michael P. Soulier <msoul...@digitaltorque.ca> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein
pgpdSQfWwDlQl.pgp
Description: PGP signature
