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

Re: [RFC PATCH] parallel-checkout: send the new object_id algo field to the workers

From
Derrick Stolee <stolee@gmail.com>
Date
May 17, 2021, 16:54 UTC
Message-ID
<7182880b-0f1e-7b3e-dc6e-b72c8ddd14b3@gmail.com>
In-Reply-To
<YJ7VI5kHAAk126YJ@camp.crustytoothpaste.net>
On 5/14/2021 3:53 PM, brian m. carlson wrote:
Show 17 quoted lines
> On 2021-05-14 at 14:36:00, Matheus Tavares wrote:>>
>> I've read the hash transition plan, but I'm not confident to say that I
>> fully understand it yet, so maybe this patch is not exactly what we need
>> here. Mainly, I'm not sure I understand in which cases we will have an
>> object_id.algo that is not the_hash_algo. Is it for the early transition
>> phases, where we have a SHA-256 repo that accepts user input as SHA-1? 
> 
> Yes, that's correct, as well as for interoperability with remotes using
> a different hash algorithm.
> 
>> Also, the object_id's copied here at send_one_item() always come from a
>> `struct cache_entry`. In this case, can they still have different
>> `algo`s or do we expect them to be the_hash_algo?
> 
> No, things in the index should always use the same algorithm..
> 
> The patch looks fine to me.
Chiming in to say I agree that this is a good patch.

Thanks, -Stolee

Previous: brian m. carlsonNext: Junio C Hamano
Message 3 of 5 in “parallel-checkout: send the new object_id algo field to the workers”
  1. parallel-checkout: send the new object_id algo field to the workersMatheus Tavares, May 14, 2021
  2. brian m. carlsonMay 14, 2021
  3. Derrick StoleeMay 17, 2021
  4. Junio C HamanoMay 17, 2021
  5. parallel-checkout: send the new object_id algo field to the workersMatheus Tavares, May 17, 2021

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.