From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2019, #01; Sat, 7)
Date: Mon, 9 Sep 2019 23:47:16 +0000 [thread overview]
Message-ID: <20190909234715.GO11334@genre.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqd0gcm2zm.fsf@gitster-ct.c.googlers.com>
[-- Attachment #1: Type: text/plain, Size: 1827 bytes --]
On 2019-09-07 at 17:26:53, Junio C Hamano wrote:
> * bc/object-id-part17 (2019-08-19) 26 commits
> - midx: switch to using the_hash_algo
> - builtin/show-index: replace sha1_to_hex
> - rerere: replace sha1_to_hex
> - builtin/receive-pack: replace sha1_to_hex
> - builtin/index-pack: replace sha1_to_hex
> - packfile: replace sha1_to_hex
> - wt-status: convert struct wt_status to object_id
> - cache: remove null_sha1
> - builtin/worktree: switch null_sha1 to null_oid
> - builtin/repack: write object IDs of the proper length
> - pack-write: use hash_to_hex when writing checksums
> - sequencer: convert to use the_hash_algo
> - bisect: switch to using the_hash_algo
> - sha1-lookup: switch hard-coded constants to the_hash_algo
> - config: use the_hash_algo in abbrev comparison
> - combine-diff: replace GIT_SHA1_HEXSZ with the_hash_algo
> - bundle: switch to use the_hash_algo
> - connected: switch GIT_SHA1_HEXSZ to the_hash_algo
> - show-index: switch hard-coded constants to the_hash_algo
> - blame: remove needless comparison with GIT_SHA1_HEXSZ
> - builtin/rev-parse: switch to use the_hash_algo
> - builtin/blame: switch uses of GIT_SHA1_HEXSZ to the_hash_algo
> - builtin/receive-pack: switch to use the_hash_algo
> - fetch-pack: use parse_oid_hex
> - patch-id: convert to use the_hash_algo
> - 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.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
next prev parent reply other threads:[~2019-09-09 23:47 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 [this message]
2019-09-10 0:19 ` Junio C Hamano
2019-09-28 23:31 ` Junio C Hamano
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=20190909234715.GO11334@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).