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

Re: current repository hash

From
Jeff King <peff@peff.net>
Date
Jun 16, 2008, 15:04 UTC
Message-ID
<20080616150416.GA6164@sigill.intra.peff.net>
In-Reply-To
<556d90580806160451g36daefb6o48b93b92589211bf@mail.gmail.com>
On Mon, Jun 16, 2008 at 01:51:52PM +0200, Alf Clement wrote:
> What would be the best command to get a unique identifier?

If you just want the commit sha1, then "git rev-list -1 HEAD" will give it to you. But take a look at git-describe, which is designed to give a nice human-readable name based on your tags.

> Do I need the 40 digit hash id?

No, but you increase your chances of a collision in the future. In practice, 8 or 9 characters tends to give unique commits.

> How can I make sure that a shorter hash id will be unique?

git-describe will find the shortest unique hash. But bear in mind that it may not be unique forever.

-Peff
Previous: Johan HerlandNext: Johannes Schindelin
Message 8 of 9 in “current repository hash”
  1. Alf ClementJun 16, 2008
  2. David TweedJun 16, 2008
  3. Santi BéjarJun 16, 2008
  4. Alf ClementJun 16, 2008
  5. Jeff KingJun 16, 2008
  6. Alf ClementJun 17, 2008
  7. Johan HerlandJun 17, 2008
  8. Jeff KingJun 16, 2008
  9. Johannes SchindelinJun 17, 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.