From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: graysongordon-gl <graysongordon1@gmail.com>,
git@vger.kernel.org, peff@peff.net, avarab@gmail.com
Subject: Re: [PATCH v7] http: add http.sslVerifyStatus to check stapled OCSP responses
Date: Wed, 23 Sep 2026 14:43:53 -0700 [thread overview]
Message-ID: <xmqq33uz7iee.fsf@gitster.g> (raw)
In-Reply-To: <arPI8PfvsKUJSypg@pks.im> (Patrick Steinhardt's message of "Wed, 23 Sep 2026 14:42:47 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> Nit: Likewise, this paragraph doesn't add much value.
>
> Other than that I'm happy with this patch. I'll leave it to you (or
> others) to decide whether this requires another reroll to address the
> two nits.
SZEDER reports breakages with this topic.
https://lore.kernel.org/git/arQ%2FnOH+o3XwQFD%2F@szeder.dev/
Since we are not in a hurry to take this topic, let me revert it out
of 'next' and give it time to mature. When the reroll comes, we can
critique these overly verbose words without much meaning again.
Thanks.
next prev parent reply other threads:[~2026-09-23 21:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 17:02 [PATCH] http: add http.sslVerifyStatus to check stapled OCSP responses graysongordon-gl
2026-08-11 19:28 ` Junio C Hamano
2026-08-11 20:44 ` [PATCH v2] " graysongordon-gl
2026-08-12 6:25 ` Patrick Steinhardt
2026-08-12 15:53 ` Grayson Gordon
2026-08-12 14:17 ` Junio C Hamano
2026-08-12 18:25 ` [PATCH v3] " graysongordon-gl
2026-08-12 21:34 ` Junio C Hamano
2026-08-13 16:06 ` Junio C Hamano
2026-08-17 18:52 ` [PATCH v4] " graysongordon-gl
2026-08-17 19:19 ` Junio C Hamano
2026-08-18 7:50 ` Patrick Steinhardt
2026-08-18 14:51 ` Grayson Gordon
2026-08-19 8:14 ` Patrick Steinhardt
2026-08-18 16:40 ` Junio C Hamano
2026-08-18 19:37 ` [PATCH v5] " graysongordon-gl
2026-08-18 20:12 ` Junio C Hamano
2026-08-18 21:22 ` Grayson Gordon
2026-08-18 21:48 ` [PATCH v6] " graysongordon-gl
2026-08-26 22:01 ` Junio C Hamano
2026-08-28 13:51 ` Grayson Gordon
2026-08-28 17:20 ` Junio C Hamano
2026-08-31 6:56 ` Patrick Steinhardt
2026-08-31 14:16 ` Junio C Hamano
2026-08-31 14:24 ` Patrick Steinhardt
2026-08-31 14:31 ` Junio C Hamano
2026-09-08 12:55 ` Grayson Gordon
2026-09-15 16:23 ` [PATCH v7] " graysongordon-gl
2026-09-16 19:29 ` Junio C Hamano
2026-09-23 12:42 ` Patrick Steinhardt
2026-09-23 21:43 ` Junio C Hamano [this message]
2026-09-23 21:07 ` SZEDER Gábor
2026-09-23 21:47 ` Junio C Hamano
2026-09-24 7:41 ` SZEDER Gábor
2026-09-24 7:59 ` Patrick Steinhardt
2026-09-25 9:28 ` SZEDER Gábor
2026-09-25 16:13 ` Junio C Hamano
2026-09-24 16:22 ` Junio C Hamano
2026-10-07 18:18 ` Junio C Hamano
2026-10-08 4:57 ` 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=xmqq33uz7iee.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=graysongordon1@gmail.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
/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