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

Re: why the 'g' prefix on the SHA1 in git-describe output?

From
LHLars Hjemli <hjemli@gmail.com>
Date
Nov 3, 2007, 13:56 UTC
Message-ID
<8c5c35580711030656h23d5910ah824de41a2cf4eafe@mail.gmail.com>
In-Reply-To
<871wb7a53d.fsf@rho.meyering.net>
On Nov 3, 2007 1:25 PM, Jim Meyering <jim@meyering.net> wrote:
> Can anyone tell me what motivated adding the 'g' prefix on the SHA1 in
> git-describe output?

I'm not sure what _motivated_ the 'g', but currently git-rev-parse understands the output from git-describe _if_ the 'g' is present.

-- larsh

Previous: Jim MeyeringNext: Andreas Ericsson
Message 2 of 4 in “why the 'g' prefix on the SHA1 in git-describe output?”
  1. Jim MeyeringNov 3, 2007
  2. Lars HjemliNov 3, 2007
  3. Andreas EricssonNov 3, 2007
  4. Jim MeyeringNov 3, 2007

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.