From: Derrick Stolee <stolee@gmail.com>
To: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Cc: Taylor Blau <me@ttaylorr.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: MIDX woes, was Re: [ANNOUNCE] Git v2.54.0-rc2
Date: Thu, 16 Apr 2026 09:24:31 -0400 [thread overview]
Message-ID: <621c9da9-2ec0-462d-ae51-0be5e0ca6ab2@gmail.com> (raw)
In-Reply-To: <20260416053435.GA646718@coredump.intra.peff.net>
On 4/16/2026 1:34 AM, Jeff King wrote:
> On Thu, Apr 16, 2026 at 01:17:33AM -0400, Jeff King wrote:
>
>> I think removing the .midx file (and optionally regenerating with the
>> old version) would be the appropriate workaround, but I wonder how hard
>> it would be to go back to generating v1 midx files by default. I know v2
>> is a building block for more advanced features, but for those who are
>> not using those features yet it is a strict regression.
>
> I think doing so is just this one-liner:
...
> and then here we need to use v2 for the new compaction feature:
...
> So that would make things work as usual for anybody mixing and matching
> multiple versions of Git, but does make life slightly worse for anybody
> who wants to use the new feature (they have to set the config). We might
> need a doc update, or possibly even to automatically default to v2 when
> using the compact command. But that could come post-2.54.
>
> At this point I'll stop poking and speculating and see what direction
> Taylor suggests. ;)
I think this is a good change to make. This fits with the standard
approach of not making breaking file changes by default, but letting
users opt-in to new versions (at least for a few major releases).
The part that is striking about Johannes' report is that this happens
on a fetch, so it is being written automatically by normal maintenance
activities in that case. Without downgrading the default version back
to a compatible version, deleting the multi-pack-index(es) will not
keep the repo in a good state.
As for the multi-pack-index being optional, I agree that we _could_
have a more graceful fallback to the pack-indexes when we don't
recognize the file format version. This should still be a very visible
warning as it can be an important performance feature, so users should
be notified when it isn't working as they expect. (This can be done
separately from this late-in-rc change for the default version.)
Thanks,
-Stolee
next prev parent reply other threads:[~2026-04-16 13:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 15:22 [ANNOUNCE] Git v2.54.0-rc2 Junio C Hamano
2026-04-15 20:50 ` MIDX woes, was " Johannes Schindelin
2026-04-15 21:04 ` Junio C Hamano
2026-04-16 5:17 ` Jeff King
2026-04-16 5:34 ` Jeff King
2026-04-16 13:24 ` Derrick Stolee [this message]
2026-04-16 16:09 ` Junio C Hamano
2026-04-16 20:29 ` Taylor Blau
2026-04-19 22:41 ` Derrick Stolee
2026-04-20 1:52 ` Junio C Hamano
2026-04-16 20:26 ` Taylor Blau
2026-04-16 23:29 ` Jeff King
2026-04-16 18:10 ` Junio C Hamano
2026-04-16 18:18 ` Junio C Hamano
2026-04-16 19:49 ` Jeff King
2026-04-16 20:12 ` Junio C Hamano
2026-04-16 23:23 ` Jeff King
2026-04-17 4:15 ` Junio C Hamano
2026-04-16 18:45 ` [PATCH] MIDX: revert the default version to v1 Junio C Hamano
2026-04-16 19:38 ` Junio C Hamano
2026-04-16 20:58 ` Junio C Hamano
2026-04-16 21:13 ` Taylor Blau
2026-04-16 20:06 ` Jeff King
2026-04-16 20:55 ` Junio C Hamano
2026-04-16 23:24 ` Jeff King
2026-04-16 23:26 ` Jeff King
2026-04-16 21:12 ` Taylor Blau
2026-04-16 23:27 ` Jeff King
2026-04-17 15:19 ` [ANNOUNCE] Git v2.54.0-rc2 Junio C Hamano
2026-04-17 17:03 ` Elijah Newren
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=621c9da9-2ec0-462d-ae51-0be5e0ca6ab2@gmail.com \
--to=stolee@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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