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

Re: Hash algorithm choice

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
Aug 9, 2009, 18:35 UTC
Message-ID
<alpine.LFD.2.01.0908091133420.3288@localhost.localdomain>
In-Reply-To
<fabb9a1e0908091116y6012caa7j6865d5fcd5d9888c@mail.gmail.com>
On Sun, 9 Aug 2009, Sverre Rabbelier wrote:
Show 5 quoted lines
>
> Wouldn't the transport code also have to be modified? I assume git's
> integrity checking would yell at if you gave it commits with
> non-sha1-hashes and have no way to tell it that that hash was
> calculated with a non-sha1-hash at clone time?

Well, if you start introducing new hashes, the assumption is that all git's that access it would have to be updated.

You certainly could never pull/push between git versions that don't know about each others hashes. But you _can_ autodetect the hash mechanism (simple: just try them all on the first object you encounter)

		Linus
Previous: Sverre RabbelierNext: Linus Torvalds
Message 5 of 8 in “Hash algorithm choice”
  1. Jerome BaumAug 9, 2009
  2. Linus TorvaldsAug 9, 2009
  3. Junio C HamanoAug 9, 2009
  4. Sverre RabbelierAug 9, 2009
  5. Linus TorvaldsAug 9, 2009
  6. Linus TorvaldsAug 9, 2009
  7. Johannes SchindelinAug 9, 2009
  8. Matthieu MoyAug 9, 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.