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

Re: [PATCH v4 3/3] Move all the SHA1 implementations into one directory

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 5, 2015, 18:29 UTC
Message-ID
<xmqq8u6c711m.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<1446705523-30701-3-git-send-email-apahlevan@ieee.org>
atousa.p@gmail.com writes:
Show 8 quoted lines
> From: Atousa Pahlevan Duprat <apahlevan@ieee.org>
>
> The various SHA1 implementations were spread around in 3 directories.
> This makes it easier to understand what implementations are
> available at a glance.
>
> Signed-off-by: Atousa Pahlevan Duprat <apahlevan@ieee.org>
> ---

I am not strongly opposed to moving block and ppc (I am not strongly for the movement, either, though).

I however think the chunked one should not be mixed together with them--it is not a full SHA-1 hash implementation but belongs to a different layer of abstration (and that is the reason why we introduced a new layer of indirection in 1/3).

Previous: atousa.p@gmail.comNext: Junio C Hamano
Message 6 of 7 in “Provide another level of abstraction for the SHA1 utilities.”
  1. 1/3 Provide another level of abstraction for the SHA1 utilities.atousa.p@gmail.com, Nov 5, 2015
  2. 2/3 Limit the size of the data block passed to SHA1_Update()atousa.p@gmail.com, Nov 5, 2015
  3. Junio C HamanoNov 5, 2015
  4. Atousa DupratNov 11, 2015
  5. 3/3 Move all the SHA1 implementations into one directoryatousa.p@gmail.com, Nov 5, 2015
  6. Junio C HamanoNov 5, 2015
  7. Junio C HamanoNov 5, 2015

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.