Re: Ambiguous ref names

Jeenu V [off-list ref] writes:

If I've two branches a.b.c and a.b.c.d, why does 'git checkout'
complains about ambiguous ref names?

Because it doesn't???

    : demo; git init
    Initialized empty Git repository in /var/tmp/gomi/twelve/.git/
    : demo/master; >f
    : demo/master; git add f
    : demo/master; git commit -a -m 'initial'
    [master (root-commit) cb1d5f2] initial
     0 files changed, 0 insertions(+), 0 deletions(-)
     create mode 100644 f
    : demo/master; git branch a.b.c
    : demo/master; git branch a.b.c.d
    : demo/master; git checkout a.b.c
    Switched to branch 'a.b.c'

It could be that you have a tag and a branch that are both named a.b.c,
though.

On Fri, Nov 20, 2009 at 3:56 PM, Junio C Hamano [off-list ref] wrote:

[...]
It could be that you have a tag and a branch that are both named a.b.c,
though.

Hm, right. But I'm getting this from an existing local repo of mine. I
can't see any tags; 'git tag -l' is empty. Is there any more info that
I can provide?

FWIW, I'm running Git under Cygwin.
-- 
:J