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

Suggestion: "git describe" pretty format

From
CGChristoph Groth <christoph@grothesque.org>
Date
Aug 13, 2018, 14:26 UTC
Message-ID
<87a7pq9wc7.fsf@grothesque.org>
Hi,

Many projects use 'git archive' to generate tarballs, especially because this functionality is exposed through gitlab/github and the like. It's also popular to base the version string on the output of 'git describe' and its variants, for example 'git describe --first-parent --dirty'.

Now while it's possible to substitute various information into the tarball using the export-subst machinery, there seems to be no way to substitute the output of 'git describe' and its variants. Specifically, when the commit being archived is untagged, there seems no way to mention an ancestral tag in the way of 'git describe'.

It seems to me that adding a pretty format for git describe would be very useful. Is there any technical reason that speaks against this?

Cheers, Christoph

Message 1 of 1 in “Suggestion: "git describe" pretty format”
  1. Christoph GrothAug 13, 2018

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.