Git development
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2026, #06)
Date: Fri, 19 Jun 2026 10:33:36 -0400	[thread overview]
Message-ID: <ajVTQPcNwaR7VM75@nand.local> (raw)
In-Reply-To: <xmqqtsr1w0z4.fsf@gitster.g>

On Wed, Jun 17, 2026 at 10:06:23AM -0700, Junio C Hamano wrote:
> * tb/midx-incremental-custom-base (2026-06-12) 3 commits
>  - midx-write: include packs above custom incremental base
>  - midx: pass custom '--base' through incremental writes
>  - t5334: expose shared `nth_line()` helper
>
>  The `git multi-pack-index write --incremental` command has been
>  corrected to properly honor the `--base` option. Previously, the
>  custom base was ignored by the normal write path, and the pack
>  exclusion logic incorrectly skipped packs from layers above the
>  selected base, breaking reachability closure for bitmaps.
>
>  Needs review.
>  source: <cover.1781294771.git.me@ttaylorr.com>

It would be nice to get this in before v2.55.0 is tagged, but I don't
think it's critical. In my analysis, the worst thing that could happen
is that generating MIDXs with a custom --base would result in a failure
to generate bitmaps, but not much else.

That's unlikely to be invoked manually, but does have the unfortunate
effect of rendering the new incremental MIDX-based repacking strategy as
useless in this release.

I'll add Peff to CC in case he has a moment to look it over.

Thanks,
Taylor

  reply	other threads:[~2026-06-19 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17 17:06 What's cooking in git.git (Jun 2026, #06) Junio C Hamano
2026-06-19 14:33 ` Taylor Blau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-06-17 17:16 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=ajVTQPcNwaR7VM75@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