git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Ambiguous ref names

From
Jeenu V <jeenuv@gmail.com>
Date
Nov 20, 2009, 10:18 UTC
Message-ID
<5195c8760911200218v5b75d690hbaaf00b44c8df6af@mail.gmail.com>
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: Junio C Hamano
Message 1 of 6 in “Ambiguous ref names”
  1. Jeenu VNov 20, 2009
  2. Junio C HamanoNov 20, 2009
  3. Jeenu VNov 20, 2009
  4. Junio C HamanoNov 20, 2009
  5. Jeenu VNov 20, 2009
  6. Jeenu VDec 11, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.