From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2020, #02; Wed, 10)
Date: Wed, 10 Jun 2020 17:27:14 -0700 [thread overview]
Message-ID: <xmqqwo4ecuql.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200610235713.GX6569@camp.crustytoothpaste.net> (brian m. carlson's message of "Wed, 10 Jun 2020 23:57:13 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> 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.
next prev parent reply other threads:[~2020-06-11 0:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 23:36 What's cooking in git.git (Jun 2020, #02; Wed, 10) Junio C Hamano
2020-06-10 23:57 ` brian m. carlson
2020-06-11 0:27 ` Junio C Hamano [this message]
2020-06-11 0:16 ` Jacob Keller
2020-06-11 1:56 ` Junio C Hamano
2020-06-17 8:07 ` Shourya Shukla
2020-06-17 8:14 ` Kaartic Sivaraam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqwo4ecuql.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.