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

Re: What's cooking in git.git (Jun 2020, #02; Wed, 10)

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 11, 2020, 00:27 UTC
Message-ID
<xmqqwo4ecuql.fsf@gitster.c.googlers.com>
In-Reply-To
<20200610235713.GX6569@camp.crustytoothpaste.net>
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
Show 9 quoted lines
> On 2020-06-10 at 23:36:30, Junio C Hamano wrote:
>> * bc/sha-256-part-2 (2020-05-27) 44 commits
>> ...
>>  - t1050: match object ID paths in a hash-insensitive way
>> 
>>  SHA-256 migration work continues.
>
> I assume you're waiting for something on this, and it's probably a
> review, but I didn't see a comment to that effect.  Am I correct?

More or less. It actually is weaker; I didn't have enough energy to give attention to the topic between issue #1 and issue #2 this month to even bother adding such a comment. By default nothing happens without input, and I try not to be the only reviewer of a large topic like this one---I always prefer to have second sets of eyes.

Thanks for working on it. A large refactoring like this one, the sooner we can absorb it, the less blocking it would be for other topics in flight.

Previous: brian m. carlsonNext: Jacob Keller
Message 3 of 7 in “What's cooking in git.git (Jun 2020, #02; Wed, 10)”
  1. Junio C HamanoJun 10, 2020
  2. brian m. carlsonJun 10, 2020
  3. Junio C HamanoJun 11, 2020
  4. Jacob KellerJun 11, 2020
  5. Junio C HamanoJun 11, 2020
  6. Shourya ShuklaJun 17, 2020
  7. Kaartic SivaraamJun 17, 2020

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.