Re: MIDX woes, was Re: [ANNOUNCE] Git v2.54.0-rc2

[Jeff King <peff@peff.net>]

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:

diff --git a/midx-write.c b/midx-write.c
index 0ff2e45aa7..607de889f9 100644
--- a/midx-write.c
+++ b/midx-write.c
@@ -1259,7 +1259,7 @@ static int write_midx_internal(struct write_midx_opts *opts)
 	struct tempfile *incr;
 	struct write_midx_context ctx = {
 		.preferred_pack_idx = NO_PREFERRED_PACK,
-		.version = MIDX_VERSION_V2,
+		.version = MIDX_VERSION_V1,
 	 };
 	struct multi_pack_index *midx_to_free = NULL;
 	int bitmapped_packs_concat_len = 0;

and there is already a midx.version config option to override it. But we
also need to touch the tests a bit. Here we just tweak the expectation
for some low-level examination of the files:

diff --git a/t/t5319-multi-pack-index.sh b/t/t5319-multi-pack-index.sh
index 58e0b685b1..ed1f993a74 100755
--- a/t/t5319-multi-pack-index.sh
+++ b/t/t5319-multi-pack-index.sh
@@ -19,9 +19,12 @@ midx_read_expect () {
 	NUM_CHUNKS=$3
 	OBJECT_DIR=$4
 	EXTRA_CHUNKS="$5"
+	# This reflects the default midx version we write; it should switch
+	# to 2 if we flip the default.
+	VERSION=1
 	{
 		cat <<-EOF &&
-		header: 4d494458 2 $HASH_LEN $NUM_CHUNKS $NUM_PACKS
+		header: 4d494458 $VERSION $HASH_LEN $NUM_CHUNKS $NUM_PACKS
 		chunks: pack-names oid-fanout oid-lookup object-offsets$EXTRA_CHUNKS
 		num_objects: $NUM_OBJECTS
 		packs:

and then here we need to use v2 for the new compaction feature:

diff --git a/t/t5335-compact-multi-pack-index.sh b/t/t5335-compact-multi-pack-index.sh
index 40f3844282..4ad007169a 100755
--- a/t/t5335-compact-multi-pack-index.sh
+++ b/t/t5335-compact-multi-pack-index.sh
@@ -57,6 +57,13 @@ test_midx_layer_object_uniqueness () {
 	done <$midx_chain
 }
 
+# MIDX compaction requires the v2 format, so make it the default
+# for the rest of this script. We check below that trying
+# compaction with v1 fails using "git -c", which will override this.
+test_expect_success 'set midx version config' '
+	git config --global midx.version 2
+'
+
 test_expect_success 'MIDX compaction with lex-ordered pack names' '
 	git init midx-compact-lex-order &&
 	(

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. ;)

-Peff