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

Re: Git describe question

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 14, 2008, 23:17 UTC
Message-ID
<7v1w1wf42n.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<487BD34F.4080201@gmx.ch>
Jean-Luc Herren <jlh@gmx.ch> writes:
Show 6 quoted lines
> Mark Burton wrote:
> ...
> I don't think people usually say "tag X is on branch Y", excepted
> maybe if Y has never been merged anywhere.  Specifically, nobody
> would say v1.5.6.3 is *on* branch master.  But it's part of its
> history.  v1.5.6.3 is *on* maint, at best.

Actually I am somewhat sympathetic to Mark here. Probably what he wants is to describe 10ce020 as v1.5.6-390-10ce020.

While that probably is doable by using the first-parent-only traversal, I do not think it is such a good idea. It is not how branches in git are designed to work. As Merlyn always says in #git at freenode, a branch is an illusion, and it is especially true in the presense of fast-forward merge (aka the upstream maintainer asking a subsystem lieutenant to do a merge for him).

Previous: Jean-Luc HerrenNext: Mark Burton
Message 5 of 6 in “Git describe question”
  1. Mark BurtonJul 14, 2008
  2. Junio C HamanoJul 14, 2008
  3. Mark BurtonJul 14, 2008
  4. Jean-Luc HerrenJul 14, 2008
  5. Junio C HamanoJul 14, 2008
  6. Mark BurtonJul 15, 2008

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.