From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] ci: work around Debian 12's HTTP/2 authentication failures
Date: Thu, 24 Sep 2026 19:22:14 -0400 [thread overview]
Message-ID: <20260924232214.GA765100@coredump.intra.peff.net> (raw)
In-Reply-To: <e94a9d4f-567e-83a0-e12a-908082365e77@gmx.de>
On Thu, Sep 24, 2026 at 08:59:24PM +0200, Johannes Schindelin wrote:
> I had GPT-6 dig deeper into the issue, since you're right: This should not
> be a CI/Debian-only gate, at the same time I didn't know what was the
> first version with the bug, so I suspected the version range to be subtly
> inaccurate. Turns out that the bug appeared first in cURL v7.88.0. So I
> adjusted your version range in preparation for the next patch iteration.
Great, it feels nicer knowing the actual start point. Your v2 patch
looks good to me!
-Peff
next prev parent reply other threads:[~2026-09-24 23:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 23:06 [PATCH] ci: work around Debian 12's HTTP/2 authentication failures Johannes Schindelin via GitGitGadget
2026-09-23 16:16 ` Junio C Hamano
2026-09-23 16:47 ` Jeff King
2026-09-23 16:53 ` Jeff King
2026-09-23 16:59 ` Jeff King
2026-09-23 17:17 ` Junio C Hamano
2026-09-23 19:25 ` Jeff King
2026-09-24 18:59 ` Johannes Schindelin
2026-09-24 19:42 ` Junio C Hamano
2026-09-24 23:22 ` Jeff King [this message]
2026-09-24 20:53 ` [PATCH v2] " Johannes Schindelin via GitGitGadget
2026-10-06 3:43 ` [PATCH] t5551: fix quoting in curl version bug prereq Jeff King
2026-10-06 3:52 ` [PATCH 2/1] test-lib: allow lazy prerequisite snippets as here-docs Jeff King
2026-10-06 9:16 ` [PATCH] t5551: fix quoting in curl version bug prereq Johannes Schindelin
2026-10-06 12:25 ` Junio C Hamano
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=20260924232214.GA765100@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.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