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

Re: Ambiguous ref names

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 20, 2009, 10:59 UTC
Message-ID
<7vpr7dzckl.fsf@alter.siamese.dyndns.org>
In-Reply-To
<5195c8760911200248v1f3d6b56q78987edfceae5541@mail.gmail.com>
Jeenu V <jeenuv@gmail.com> writes:
Show 8 quoted lines
> On Fri, Nov 20, 2009 at 3:56 PM, Junio C Hamano <gitster@pobox.com> 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?
man git-for-each-ref?
Previous: Jeenu VNext: Jeenu V
Message 4 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.