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

Re: [PATCH v4 2/3] Limit the size of the data block passed to SHA1_Update()

From
Atousa Duprat <atousa.p@gmail.com>
Date
Nov 11, 2015, 23:46 UTC
Message-ID
<CA+izobv=PUf+6WWfQNEO+bwfzLRQ3V-TKQdUS0-qNJ0aCSkJzA@mail.gmail.com>
In-Reply-To
<xmqqtwp05mgn.fsf@gitster.mtv.corp.google.com>
> Adjusting to the proposed change to 1/3, this step would become the
> attached patch.  Note that I thought the above would not scale well
> so I did it a bit differently.

Thank you, I understand now the changes that you made. Let me know if this can be improved any further.

Atousa
Previous: Junio C HamanoNext: atousa.p@gmail.com
Message 4 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.