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

Re: Hash algorithm choice

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Aug 9, 2009, 18:44 UTC
Message-ID
<vpq1vnkddy2.fsf@bauges.imag.fr>
In-Reply-To
<f448a46a0908090917s102b4c83pbad6f298a8e127cc@mail.gmail.com>
Jerome Baum <jerome@jeromebaum.com> writes:
> How difficult would it be to allow users to choose a hash function
> during git-init which is then globally used in the repo?

There's at least one really difficult thing: how do you merge two projects using two different hash functions? The Git repository, for example, has several (I don't remember how many) root repository, and was originally made of several projects (git, gitk, git gui, ...). If these projects had started using different hash functions, then, either:

* Git would have needed to learn how to merge, and record the merge
  history, of projects using different hash functions.
* One of the projects would have been forced to be converted to
  another hash function, which means changing all its identifiers (so,
  for example, finding a message on gmane telling that commit 1ab23cde
  fixes your problem wouldn't help much anymore ...).
-- 
Matthieu
Previous: Johannes Schindelin
Message 8 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.