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

Re: "git describe" documentation and behavior mismatch

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 3, 2017, 05:39 UTC
Message-ID
<xmqqefocjrp2.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CACx-yZ1dJuUj5mD6WE8yqZCPMK8q-yaJ0GKUSppZ7uDkqvJ5UA@mail.gmail.com>
Daniel Knittl-Frank <knittl89@googlemail.com> writes:
Show 5 quoted lines
> An interesting fact (and intentional behavior?) is that describing a
> commit with only a lightweight tag will properly display the tags/
> prefix. I assume this is because the annotated tags only store the
> tagname without any ref namespace, which is then picked up by git
> describe and displayed.

I suspect that "see if the name recorded in the tag object matches the name of the ref that stores the tag after refs/tags/" code *is* not just verifying what it claims to (which may be good) but also unintentionally affecting the output (i.e. "--all" promises that the prefix tags/ should be shown). Perhaps the code needs to be fixed if that is the case.

Previous: Daniel Knittl-FrankNext: Daniel Knittl-Frank
Message 3 of 6 in “"git describe" documentation and behavior mismatch”
  1. Daniel Knittl-FrankNov 30, 2017
  2. Daniel Knittl-FrankNov 30, 2017
  3. Junio C HamanoDec 3, 2017
  4. Daniel Knittl-FrankDec 11, 2017
  5. Daniel Knittl-FrankDec 11, 2017
  6. Junio C HamanoDec 15, 2017

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.