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

Re: Suggestion: drop 'g' in git-describe suffix

From
Andy Whitcroft <apw@shadowen.org>
Date
Nov 2, 2006, 11:12 UTC
Message-ID
<4549D2A7.7000209@shadowen.org>
In-Reply-To
<4549CE2A.3010808@xs4all.nl>
Han-Wen Nienhuys wrote:
Show 31 quoted lines
> Andy Whitcroft escreveu:
>> Han-Wen Nienhuys wrote:
>>> Andy Whitcroft escreveu:
>>>>> or some other non-hex character.
>>>> g is not a hex digit, hex is 0-f ??
>>>>
>>> Yes of course; silly me. Still I think it would be clearer if it used a
>>> non-alphabet char, eg.
>>>
>>>   tag+sha1
>>>
>>> to separate the tag and the committish.
>>
>> Well there is a non-alphabet character in there, a minus (-).  The g
>> prefix on the sha1 _fragment_ it to indicate that it is in fact a
>> truncated sha1, not a complete one.  
> 
> is this policy documented somewhere?  None of the tools understand it.
> 
> [lilydev@haring git]$ git describe
> v1.4.3.3-g1e1f76e
> [lilydev@haring git]$ git show g1e1f76e
> fatal: ambiguous argument 'g1e1f76e': unknown revision or path not in
> the working tree.
> Use '--' to separate paths from revisions
> 
> My suggestion is to use
> 
>   v1.4.3.3+1e1f76e
> 
> here.
The 'whole' thing is valid as an object reference:
apw@pinky$ git describe
v1.4.3.3-g8cf249b
apw@pinky$ git show v1.4.3.3-g8cf249b
commit 8cf249b755c257ea19100b888ac612e601cdf96b
Merge: 15c3ffb... fa438a2...
[...]
Previous: Nicolas Vilz 'niv'Next: Petr Baudis
Message 17 of 19 in “Suggestion: drop 'g' in git-describe suffix”
  1. Han-Wen NienhuysNov 2, 2006
  2. Andy WhitcroftNov 2, 2006
  3. Han-Wen NienhuysNov 2, 2006
  4. Andy WhitcroftNov 2, 2006
  5. Han-Wen NienhuysNov 2, 2006
  6. Johannes SchindelinNov 2, 2006
  7. Santi BéjarNov 2, 2006
  8. Andy WhitcroftNov 2, 2006
  9. Santi BéjarNov 2, 2006
  10. Andy WhitcroftNov 2, 2006
  11. Han-Wen NienhuysNov 2, 2006
  12. Santi BéjarNov 2, 2006
  13. Jakub NarebskiNov 2, 2006
  14. Nicolas Vilz 'niv'Nov 2, 2006
  15. Johannes SchindelinNov 2, 2006
  16. Nicolas Vilz 'niv'Nov 2, 2006
  17. Andy WhitcroftNov 2, 2006
  18. Petr BaudisNov 2, 2006
  19. Carl WorthNov 2, 2006

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.