public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Taylor Blau <me@ttaylorr.com>,  git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2026, #05)
Date: Wed, 18 Mar 2026 09:36:52 -0700	[thread overview]
Message-ID: <xmqqfr5xgkm3.fsf@gitster.g> (raw)
In-Reply-To: <20260318030304.GA1926419@coredump.intra.peff.net> (Jeff King's message of "Tue, 17 Mar 2026 23:03:04 -0400")

Jeff King <peff@peff.net> writes:

> On Mon, Mar 16, 2026 at 06:07:41PM -0400, Taylor Blau wrote:
>
>> 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
>> ...
>> >  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.
>
> Yeah, I looked over the range-diff for v3 and didn't have anything
> further to add.

Thanks.

      reply	other threads:[~2026-03-18 16:36 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
2026-03-18  3:03   ` Jeff King
2026-03-18 16:36     ` Junio C Hamano [this message]

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=xmqqfr5xgkm3.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.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