From: Jeenu V <jeenuv@gmail.com>
To: git@vger.kernel.org
Subject: Ambiguous ref names
Date: Fri, 20 Nov 2009 15:48:44 +0530 [thread overview]
Message-ID: <5195c8760911200218v5b75d690hbaaf00b44c8df6af@mail.gmail.com> (raw)
Hi,
I'm re-posting this from the git-users Google Groups:
If I've two branches a.b.c and a.b.c.d, why does 'git checkout'
complains about ambiguous ref names? 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?
--
:J
next reply other threads:[~2009-11-20 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 10:18 Jeenu V [this message]
2009-11-20 10:26 ` Ambiguous ref names Junio C Hamano
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=5195c8760911200218v5b75d690hbaaf00b44c8df6af@mail.gmail.com \
--to=jeenuv@gmail.com \
--cc=git@vger.kernel.org \
/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