From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] t5702: be more resilient to env quoting
Date: Fri, 30 Oct 2026 20:12:06 -0700 [thread overview]
Message-ID: <xmqqwlqytvg9.fsf@gitster.g> (raw)
In-Reply-To: <20261031002550.GA626623@coredump.intra.peff.net> (Jeff King's message of "Fri, 30 Oct 2026 20:25:50 -0400")
Jeff King <peff@peff.net> writes:
> The new coreutils hit Debian unstable, so I ran into this doing my usual
> daily "make test". I wondered what idiot did the overly-complicated
> "env" invocation in the first place, but naturally it turns out it was
> me.
Namely, in eaa0fd6584 (git_connect(): fix corner cases in
downgrading v2 to v0, 2023-03-17). The log message starts by
discussing dropping a "push" that asks for v2 to v0 because we can
only do v2 for fetches, but the three tests added by the patch
verify that fetch, push, and archive invoked via a custom path do
not request v2.
I can see that the patch correctly checks the value of '$GIT_PROTOCOL'
in the environment when these custom commands are invoked. I would
have to read the log message for the "head-scratching notes" in
eaa0fd6584 if I wanted to remind myself why the original code wanted
to downgrade a custom upload-pack to v0 in the first place. Luckily,
I do not have to do that to be convinced that this particular patch
is correct.
next prev parent reply other threads:[~2026-10-31 3:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 0:25 [PATCH] t5702: be more resilient to env quoting Jeff King
2026-10-31 2:03 ` Todd Zullinger
2026-10-31 5:06 ` Jeff King
2026-10-31 5:08 ` Collin Funk
2026-10-31 5:21 ` Collin Funk
2026-10-31 3:12 ` Junio C Hamano [this message]
2026-10-31 5:03 ` Jeff King
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=xmqqwlqytvg9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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