From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Taylor Blau <me@ttaylorr.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] MIDX: revert the default version to v1
Date: Thu, 16 Apr 2026 13:55:46 -0700 [thread overview]
Message-ID: <xmqq5x5qzktp.fsf@gitster.g> (raw)
In-Reply-To: <20260416200659.GB1887222@coredump.intra.peff.net> (Jeff King's message of "Thu, 16 Apr 2026 16:06:59 -0400")
Jeff King <peff@peff.net> writes:
> On Thu, Apr 16, 2026 at 11:45:49AM -0700, Junio C Hamano wrote:
>
>> From: Jeff King <peff@peff.net>
>>
>> Dscho reports that fetching into a repository with Git 2.54-rc2 made
>> it unusable with Git 2.53, as the recent code by default writes
>> version 2 multi-pack-index files. Version 2 is the base of more
>> advanced features to come, but using it where these features are not
>> used is a strict regression.
>>
>> As deployed versions of Git and its reimplementations may not be
>> ready for the format bump, let's revert the default version of MIDX
>> file we write back to V1, and adjust tests that exercise V2-specific
>> features to explicitly request V2.
>>
>> Signed-off-by: Junio C Hamano <gitster@pobox.com>
>
> This looks fine to me, and you can add my S-o-b if you want. But let me
> propose a slight alternative that reduces the test churn and may make
> things easier going forward.
I did merge it to 'jch' (which I also tested externally) and then
'next', but haven't pushed out the 'next' integration out to test it
externally, so I'll chuck it and replace it with this version, as
the "compact is the only thing that needs v2" sound like a better
workaround.
> diff --git a/midx-write.c b/midx-write.c
> index 0ff2e45aa7..a89ac53045 100644
> --- a/midx-write.c
> +++ b/midx-write.c
> @@ -1259,7 +1259,6 @@ 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,
> };
> struct multi_pack_index *midx_to_free = NULL;
> int bitmapped_packs_concat_len = 0;
> @@ -1275,6 +1274,9 @@ static int write_midx_internal(struct write_midx_opts *opts)
> ctx.repo = r;
> ctx.source = opts->source;
>
> + ctx.version = opts->flags & MIDX_WRITE_COMPACT ?
> + MIDX_VERSION_V2 :
> + MIDX_VERSION_V1;
Just a sytle thing but I'd prefer to see this written like this:
+ ctx.version = ((opts->flags & MIDX_WRITE_COMPACT)
+ ? MIDX_VERSION_V2
+ : MIDX_VERSION_V1);
because you do not have to worry about the precedence between & and
?: with an extra (parentheses), and a ternary split into multiple
lines is easier to spot if you write it at the beginning of the
line, with ? and : aligned.
next prev parent reply other threads:[~2026-04-16 20:55 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
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 [this message]
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=xmqq5x5qzktp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--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