From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: What's cooking in git.git (Jan 2025, #06; Wed, 22)
Date: Thu, 23 Jan 2025 12:36:56 -0500 [thread overview]
Message-ID: <Z5J+ONavA9XUTPn1@nand.local> (raw)
In-Reply-To: <xmqqbjvyv510.fsf@gitster.g>
On Wed, Jan 22, 2025 at 02:48:43PM -0800, Junio C Hamano wrote:
> * tb/unsafe-hash-cleanup (2025-01-17) 8 commits
> - hash.h: drop unsafe_ function variants
> - csum-file: introduce hashfile_checkpoint_init()
> - t/helper/test-hash.c: use unsafe_hash_algo()
> - csum-file.c: use unsafe_hash_algo()
> - hash.h: introduce `unsafe_hash_algo()`
> - csum-file.c: extract algop from hashfile_checksum_valid()
> - csum-file: store the hash algorithm as a struct field
> - t/helper/test-tool: implement sha1-unsafe helper
>
> The API around choosing to use unsafe variant of SHA-1
> implementation has been updated in an attempt to make it harder to
> abuse.
>
> Expecting a hopefully small and final reroll.
> cf. <20250118124343.GA3828177@coredump.intra.peff.net>
> source: <cover.1737151386.git.me@ttaylorr.com>
Thanks for the nudge. I sent out a very small reroll of this series as
<cover.1737653640.git.me@ttaylorr.com>.
> * tb/incremental-midx-part-2 (2024-11-20) 15 commits
> - midx: implement writing incremental MIDX bitmaps
> - pack-bitmap.c: use `ewah_or_iterator` for type bitmap iterators
> - pack-bitmap.c: keep track of each layer's type bitmaps
> - ewah: implement `struct ewah_or_iterator`
> - pack-bitmap.c: apply pseudo-merge commits with incremental MIDXs
> - pack-bitmap.c: compute disk-usage with incremental MIDXs
> - pack-bitmap.c: teach `rev-list --test-bitmap` about incremental MIDXs
> - pack-bitmap.c: support bitmap pack-reuse with incremental MIDXs
> - pack-bitmap.c: teach `show_objects_for_type()` about incremental MIDXs
> - pack-bitmap.c: teach `bitmap_for_commit()` about incremental MIDXs
> - pack-bitmap.c: open and store incremental bitmap layers
> - pack-revindex: prepare for incremental MIDX bitmaps
> - Documentation: describe incremental MIDX bitmaps
> - Merge branch 'tb/pseudo-merge-bitmap-fixes' into tb/incremental-midx-part-2
> - Merge branch 'tb/incremental-midx-part-1' into tb/incremental-midx-part-2
>
> Incrementally updating multi-pack index files.
>
> Needs review.
> source: <cover.1732054032.git.me@ttaylorr.com>
Yeah, I would really like to see this one progress. I'll gently nudge
Peff (CC'd) as a potential reviewer here.
> * ds/name-hash-tweaks (2024-12-20) 8 commits
> - pack-objects: add third name hash version
> - pack-objects: prevent name hash version change
> - test-tool: add helper for name-hash values
> - p5313: add size comparison test
> - pack-objects: add GIT_TEST_NAME_HASH_VERSION
> - repack: add --name-hash-version option
> - pack-objects: add --name-hash-version option
> - pack-objects: create new name-hash function version
>
> "git pack-objects" and its wrapper "git repack" learned an option
> to use an alternative path-hash function to improve delta-base
> selection to produce a packfile with deeper history than window
> size.
>
> Will merge to 'next'.
> (microhalt) <Z5E5KdbwHE7fmiJx@nand.local>
> source: <pull.1823.v3.git.1734715194.gitgitgadget@gmail.com>
Hmm. I think that the first seven patches are fine as-is (I had some
minor comments on them, but as I noted they are mostly cosmetic and
don't require a reroll IMHO). But I think it would be worth having a
more thorough discussion about the last patch, or at least to hear from
Stolee before proceeding.
Thanks,
Taylor
next prev parent reply other threads:[~2025-01-23 17:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 22:48 What's cooking in git.git (Jan 2025, #06; Wed, 22) Junio C Hamano
2025-01-23 0:36 ` Jeff King
2025-01-23 1:52 ` Junio C Hamano
2025-01-31 23:34 ` Jeff King
2025-01-31 23:39 ` Jeff King
2025-01-31 23:49 ` Junio C Hamano
2025-02-01 2:29 ` Jeff King
2025-02-02 23:39 ` Junio C Hamano
2025-02-03 13:51 ` Junio C Hamano
2025-02-04 2:35 ` Jeff King
2025-02-02 18:09 ` D. Ben Knoble
2025-02-02 23:33 ` Junio C Hamano
2025-02-03 15:33 ` Jeff King
2025-01-23 0:38 ` Eric Sunshine
2025-01-23 1:53 ` Junio C Hamano
2025-01-23 17:36 ` Taylor Blau [this message]
2025-01-24 6:07 ` Patrick Steinhardt
2025-01-24 12:55 ` Toon Claes
2025-01-24 17:05 ` Junio C Hamano
2025-01-24 16:02 ` Junio C Hamano
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=Z5J+ONavA9XUTPn1@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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 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 NNTP newsgroup(s).