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

Re: Hash algorithm choice

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Aug 9, 2009, 18:16 UTC
Message-ID
<fabb9a1e0908091116y6012caa7j6865d5fcd5d9888c@mail.gmail.com>
In-Reply-To
<7vljls986b.fsf@alter.siamese.dyndns.org>
Heya,
On Sun, Aug 9, 2009 at 11:03, Junio C Hamano<gitster@pobox.com> wrote:
> Just in case Jerome really wants to go further, "almost no changes" and
> "minimal" refers to the fact that we have a few hard-coded hash values
> known to the code, such as the object name for an empty blob and an empty
> tree.

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?

-- 
Cheers,

Sverre Rabbelier
Previous: Junio C HamanoNext: Linus Torvalds
Message 4 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.