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

Re: [PATCH] Teach git-describe --long to output always the long format

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 25, 2008, 03:08 UTC
Message-ID
<7vwsotpwbr.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20080225023634.GK8410@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> writes:
Show 6 quoted lines
>> +		else
>> +			printf("%s-0-g%s\n", n->path,
>> +				find_unique_abbrev(cmit->object.sha1, abbrev));
>
> Is this really that useful?  Where is having the tag and the commit
> SHA-1 both useful?

I had the same question. The only place that I find this could be useful is when you tag, build and install, and then find glitches before pushing the results out and rewind, rebuild and re-tag. I unfortunately have this issue almost all the time.

But even then, I would probably not rely on this patch.
Previous: Shawn O. PearceNext: Santi Béjar
Message 3 of 12 in “Teach git-describe --long to output always the long format”
  1. Teach git-describe --long to output always the long formatSanti Béjar, Feb 24, 2008
  2. Shawn O. PearceFeb 25, 2008
  3. Junio C HamanoFeb 25, 2008
  4. Santi BéjarFeb 25, 2008
  5. Junio C HamanoFeb 25, 2008
  6. Santi BéjarFeb 25, 2008
  7. Junio C HamanoFeb 25, 2008
  8. Santi BéjarFeb 25, 2008
  9. Junio C HamanoFeb 26, 2008
  10. Santi BéjarFeb 26, 2008
  11. Jakub NarebskiFeb 25, 2008
  12. Teach git-describe --long to output always the long formatSanti Béjar, Feb 25, 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.