git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Elijah Newren <newren@gmail.com>, Jeff King <peff@peff.net>,
	git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2025, #07; Wed, 26)
Date: Wed, 26 Mar 2025 13:19:17 -0400	[thread overview]
Message-ID: <Z+Q3FUCcsPETzVBs@nand.local> (raw)
In-Reply-To: <xmqqiknwhsdz.fsf@gitster.g>

On Wed, Mar 26, 2025 at 05:46:00AM -0700, Junio C Hamano wrote:
> * tb/incremental-midx-part-2 (2025-03-21) 14 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
>  - Documentation: remove a "future work" item from the MIDX docs
>
>  Incrementally updating multi-pack index files.
>
>  Comments?
>  source: <cover.1742493373.git.me@ttaylorr.com>

I think that this one is ready to go. Elijah was satisfied[1] with the
changes between v4->v5. Peff looked at v4 and seemed generally
satisfied[2], and I think the changes he suggested were faithfully
implemented in v5.

If either have thoughts or think that it shouldn't be merged yet, I'm
more than happy to keep plugging away at this one, but I suspect it's
ready to start being merged down.

Thanks,
Taylor

[1]: https://lore.kernel.org/git/CABPp-BGv_KDdviT0C6khs0gaoHLSt+ZfmbAVrAkTyT9PC1=Unw@mail.gmail.com/
[2]: https://lore.kernel.org/git/20250318022134.GD1473033@coredump.intra.peff.net/

  reply	other threads:[~2025-03-26 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 12:46 What's cooking in git.git (Mar 2025, #07; Wed, 26) Junio C Hamano
2025-03-26 17:19 ` Taylor Blau [this message]
2025-03-26 18:09   ` Jeff King
2025-03-29  0:34 ` D. Ben Knoble
2025-04-08 22:39   ` D. Ben Knoble
2025-04-08 22:49     ` Junio C Hamano
2025-04-04  8:58 ` jk/fetch-follow-remote-head-fix, was " Jeff King
2025-04-05 21:11   ` Bence Ferdinandy
2025-04-04  9:02 ` jk/zlib-inflate-fixes, " Jeff King

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=Z+Q3FUCcsPETzVBs@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=newren@gmail.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).