From: Junio C Hamano <gitster@pobox.com>
To: Jeenu V <jeenuv@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Ambiguous ref names
Date: Fri, 20 Nov 2009 02:26:42 -0800 [thread overview]
Message-ID: <7vzl6h3319.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <5195c8760911200218v5b75d690hbaaf00b44c8df6af@mail.gmail.com> (Jeenu V.'s message of "Fri\, 20 Nov 2009 15\:48\:44 +0530")
Jeenu V <jeenuv@gmail.com> 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.
next prev parent reply other threads:[~2009-11-20 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 10:18 Ambiguous ref names Jeenu V
2009-11-20 10:26 ` Junio C Hamano [this message]
2009-11-20 10:48 ` Jeenu V
2009-11-20 10:59 ` Junio C Hamano
2009-11-20 11:55 ` Jeenu V
2009-12-11 8:03 ` Jeenu V
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vzl6h3319.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jeenuv@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox