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

Re: [PATCH] gitweb: recognize six digit abbreviated SHA1

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 13, 2009, 08:26 UTC
Message-ID
<7vd4erd32a.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<496BF5D7.2090003@vilain.net>
Sam Vilain <sam@vilain.net> writes:
Show 5 quoted lines
> I think if you're going to go so short as 6 digits, it's probably worth
> making sure that the really short SHA1s check commits only. eg, if
> you've got a commit 'fa023473' and a tree 'fa023421', then 'fa0234'
> should match the commit and not the tree. But I don't think there's a
> plumbing way to do a query like that at the moment.

When people give an abbreviated object name, 99% of the time they mean commits (and "index deadbeef..acebead" in a patch is a good place to pick blob object names from, which would be what the 99% of the remaining 1% would name), so making sure it is a commit or a blob would be a very sensible thing to do.

Unfortunately, you fundamentally cannot do this without taking a performance hit of actually opening the object.

Previous: Sam VilainNext: Sam Vilain
Message 4 of 5 in “gitweb: recognize six digit abbreviated SHA1”
  1. gitweb: recognize six digit abbreviated SHA1Anders Melchiorsen, Jan 13, 2009
  2. Anders MelchiorsenJan 13, 2009
  3. Sam VilainJan 13, 2009
  4. Junio C HamanoJan 13, 2009
  5. Sam VilainJan 14, 2009

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.