From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2026, #05)
Date: Mon, 16 Mar 2026 18:07:41 -0400 [thread overview]
Message-ID: <abh/LUGAWUDx/E2t@nand.local> (raw)
In-Reply-To: <xmqqh5qka8so.fsf@gitster.g>
On Thu, Mar 12, 2026 at 05:10:31PM -0700, Junio C Hamano wrote:
> * tb/incremental-midx-part-3.2 (2026-02-24) 17 commits
> - midx: enable reachability bitmaps during MIDX compaction
> - midx: implement MIDX compaction
> - t/helper/test-read-midx.c: plug memory leak when selecting layer
> - midx-write.c: factor fanout layering from `compute_sorted_entries()`
> - midx-write.c: enumerate `pack_int_id` values directly
> - midx-write.c: extract `fill_pack_from_midx()`
> - midx-write.c: introduce `midx_pack_perm()` helper
> - midx: do not require packs to be sorted in lexicographic order
> - midx-write.c: introduce `struct write_midx_opts`
> - midx-write.c: don't use `pack_perm` when assigning `bitmap_pos`
> - t/t5319-multi-pack-index.sh: fix copy-and-paste error in t5319.39
> - git-multi-pack-index(1): align SYNOPSIS with 'git multi-pack-index -h'
> - git-multi-pack-index(1): remove non-existent incompatibility
> - builtin/multi-pack-index.c: make '--progress' a common option
> - midx: introduce `midx_get_checksum_hex()`
> - midx: rename `get_midx_checksum()` to `midx_get_checksum_hash()`
> - midx: mark `get_midx_checksum()` arguments as const
>
> Further work on incremental repacking using MIDX/bitmap
>
> Will merge to 'next'?
> source: <cover.1771959555.git.me@ttaylorr.com>
I think that this one is ready to go. There was a relatively small
range-diff between v2 and v3 based on Peff's review of the earlier
round.
That review[1] said that:
There were a couple minor issues brought up in review, like
out-dated comments and the u32_add interface. So I think we might
need a v3 with a few touch-ups, but that's it.
, so I think with the latest round we should be OK to start merging this
one down.
Thanks,
Taylor
[1]: https://lore.kernel.org/git/20260223140847.GB271392@coredump.intra.peff.net/
next prev parent reply other threads:[~2026-03-16 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 0:10 What's cooking in git.git (Mar 2026, #05) Junio C Hamano
2026-03-13 0:24 ` Jeff King
2026-03-13 4:24 ` Junio C Hamano
2026-03-16 9:34 ` Patrick Steinhardt
2026-03-16 22:07 ` Taylor Blau [this message]
2026-03-18 3:03 ` Jeff King
2026-03-18 16:36 ` 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=abh/LUGAWUDx/E2t@nand.local \
--to=me@ttaylorr.com \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox