From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2023, #06; Fri, 23)
Date: Fri, 23 Jun 2023 16:22:42 -0700 [thread overview]
Message-ID: <xmqqo7l59325.fsf@gitster.g> (raw)
In-Reply-To: <xmqq1qi1aix3.fsf@gitster.g> (Junio C. Hamano's message of "Fri, 23 Jun 2023 15:54:48 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> * jk/redact-h2h3-headers-fix (2023-06-17) 1 commit
> (merged to 'next' on 2023-06-20 at c1247fd527)
> + http: handle both "h2" and "h2h3" in curl info lines
>
> Curl library recently changed how http2 traces are shown and broke
> the code to redact sensitive info header, which has been fixed.
>
> Will merge to 'master'.
> source: <20230617051559.GD562686@coredump.intra.peff.net>
Even though this hasn't spent the usual 1 calendar week days in
'next', I am inclined to fast-track merge it to 'master' (and
probably to 'maint'), as GitHub actions CI currently is broken
with any branch without this fix for macOS jobs.
next prev parent reply other threads:[~2023-06-23 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 22:54 What's cooking in git.git (Jun 2023, #06; Fri, 23) Junio C Hamano
2023-06-23 23:22 ` Junio C Hamano [this message]
2023-06-24 1:18 ` 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=xmqqo7l59325.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).