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

Re: [PATCH/RFC] make the new block-sha1 the default

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 25, 2009, 06:50 UTC
Message-ID
<7vprakpett.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20090825041859.GA10033@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 8 quoted lines
> On Mon, Aug 24, 2009 at 11:04:37PM -0400, Nicolas Pitre wrote:
>
>> ... and remove support for linking against the openssl SHA1 code.
>> 
>> The block-sha1 implementation is not significantly worse and sometimes 
>> even faster than the openssl SHA1 implementation.  This allows for
>
> Is there a reason not to leave the option of linking against openssl?
I think it is a valid question.  Why remove the _option_?
I would certainly understand it if you made BLK_SHA1 the _default_, though.
Previous: Jeff KingNext: Nicolas Pitre
Message 3 of 4 in “make the new block-sha1 the default”
  1. make the new block-sha1 the defaultNicolas Pitre, Aug 25, 2009
  2. Jeff KingAug 25, 2009
  3. Junio C HamanoAug 25, 2009
  4. Nicolas PitreAug 25, 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.