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

Re: Git describe question

From
MBMark Burton <markb@ordern.com>
Date
Jul 14, 2008, 08:20 UTC
Message-ID
<20080714092040.4090046b@crow>
In-Reply-To
<7vvdz8hp3d.fsf@gitster.siamese.dyndns.org>
Thanks for the speedy response.
> A longer answer.  v1.5.6.X releases are from 'maint'.  The branch has
> forked from the mainline loooong time ago (at v1.5.6, to be exact), and
> has only fixes.  'master' is a separate branch for development that would
> eventually lead to the next major release (planned to be v1.6.0).

Ok, I understand what it's doing now - but that makes me wonder if it would be useful/possible to be able to specify that git describe only considers the commits on top of the tag for the current (or some specified branch). i.e. at the moment, gitk shows 8 commits on top of v1.5.6.3 in the master branch.

As the master branch is the checked out branch and the v1.5.6.3 tag tags a commit in that branch (via the merge) is it not possible to only consider the commits between the tag and the HEAD on that branch?

Sorry, I don't understand the git internals (yet) so I don't know if this is a stupid question and I am certainly not in a position to try and implement it myself (yet).

Cheers,
Mark
Previous: Junio C HamanoNext: Jean-Luc Herren
Message 3 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.