Re: RFC v3: Another proposed hash function transition plan

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 14, 2017, 02:13 UTC
Message-ID: <xmqqpoauyqlp.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <20170913221854.GP27425@aiede.mtv.corp.google.com>

Jonathan Nieder <jrnieder@gmail.com> writes:

Show 5 quoted lines

> In other words, a long lifetime for the hash absolutely is a design
> goal.  Coping well with an unexpectedly short lifetime for the hash is
> also a design goal.
>
> If the hash function lasts 10 years then I am happy.

Absolutely. When two functions have similar expected remaining life and are equally widely supported, then faster is better than slower. Otherwise our primary goal when picking the function from candidates should be to optimize for its remaining life and wider availability.

Thanks.

$ 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.