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 (Sep 2019, #01; Sat, 7)
Date: Sun, 29 Sep 2019 08:31:33 +0900 [thread overview]
Message-ID: <xmqq36ggj8ve.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190909234715.GO11334@genre.crustytoothpaste.net> (brian m. carlson's message of "Mon, 9 Sep 2019 23:47:16 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> On 2019-09-07 at 17:26:53, Junio C Hamano wrote:
>> * bc/object-id-part17 (2019-08-19) 26 commits
>> ...
>> - builtin/replace: make hash size independent
>>
>> Preparation for SHA-256 upgrade continues.
>>
>> Looked mostly OK, with a possible update.
>> cf. <20190820223606.GJ365197@genre.crustytoothpaste.net>
>
> Just to update on the status of this, I wasn't planning on a reroll,
> although I'm happy to do so if folks have feedback. Opinions for or
> against the current state are welcome.
I've already said that this looked mostly OK, and I think you and
RRéne's "maybe adopt the use of oid_to_hex()s without using our own
buffer" can come after the dust settles, so let's move this forward
as-is.
That is, unless I hear otherwise in the next few days.
Thanks.
next prev parent reply other threads:[~2019-09-28 23:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 17:26 What's cooking in git.git (Sep 2019, #01; Sat, 7) Junio C Hamano
2019-09-09 18:58 ` Denton Liu
2019-09-09 19:57 ` Junio C Hamano
2019-09-10 0:18 ` Denton Liu
2019-09-09 23:47 ` brian m. carlson
2019-09-10 0:19 ` Junio C Hamano
2019-09-28 23:31 ` Junio C Hamano [this message]
2019-09-28 23:35 ` brian m. carlson
2019-09-10 5:04 ` Martin Ågren
2019-09-10 18:23 ` Josh Steadmon
2019-09-11 1:03 ` Matheus Tavares Bernardino
2019-09-11 12:01 ` pd/fetch-jobs, was " Johannes Schindelin
2019-09-12 18:02 ` Junio C Hamano
2019-09-14 13:58 ` Palmer Dabbelt
2019-09-16 17:43 ` Junio C Hamano
2019-09-16 20:40 ` Palmer Dabbelt
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq36ggj8ve.fsf@gitster-ct.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).