From: Jeff King <peff@peff.net>
To: Taylor Blau <me@ttaylorr.com>
Cc: Junio C Hamano <gitster@pobox.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 19:27:55 -0400 [thread overview]
Message-ID: <20260416232755.GC1904316@coredump.intra.peff.net> (raw)
In-Reply-To: <aeFQvu4iqJAQMjCy@nand.local>
On Thu, Apr 16, 2026 at 05:12:30PM -0400, Taylor Blau wrote:
> > As a result, writing a midx with Git 2.54-rc2 puts the repository into a
> > state that is unusable with Git 2.53. And this midx write may happen
> > behind the scenes as part of normal operations, like fetch.
>
> I'm not sure if it's worth mentioning, but I think that it's reasonable
> to say "Git 2.53 and earlier", with the implied lower bound being which
> version first introduced the MIDX. I think it's equally fine as-is,
> though.
Yeah, that is a little more clear. Looks like it's been pushed out to
next already, though.
> > I have a feeling there are probably some gaps in v2 testing in t5319,
> > since we are no longer using v2 for the bulk of the tests. IMHO that is
> > OK to sort out post-release.
>
> Perhaps, although you could make the opposite argument for v1 MIDXs
> when we previously switched the default to write v2 MIDXs. The format
> differs only in the version field, and the ordering constraints on the
> packs within the MIDX. That area and the compatibility issues here are
> the "interesting" parts to test IMHO.
I think that t5319 specifically writes a few midxs with v1 to test the
ordering constraints. Probably there should now be some v2 specific
tests in the same way. I was hoping you could pick up the pieces there,
post-2.54.
-Peff
next prev parent reply other threads:[~2026-04-16 23:27 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
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 [this message]
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=20260416232755.GC1904316@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
/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