From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Stanislav Malishevskiy via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org,
Stanislav Malishevskiy <stanislav.malishevskiy@gmail.com>,
Stanislav Malishevskiy <s.malishevskiy@auriga.com>
Subject: Re: [PATCH v2] http: add support for different sslcert and sslkey types.
Date: Tue, 21 Mar 2023 10:43:12 -0700 [thread overview]
Message-ID: <xmqqjzzahufj.fsf@gitster.g> (raw)
In-Reply-To: <20230321172223.GA3119834@coredump.intra.peff.net> (Jeff King's message of "Tue, 21 Mar 2023 13:22:23 -0400")
Jeff King <peff@peff.net> writes:
> 2. Add a specific "test with https" script that covers some basic
> tests (possibly even just including t5551, in the same way t5559
> does). If the platform apache doesn't support ssl, then it should
> fail gracefully. And then we could add more SSL specific tests
> to that script.
Both choices sound sensible. This second one may be simpler to
arrange.
Thanks.
next prev parent reply other threads:[~2023-03-21 17:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 13:51 [PATCH] That change for support different sslcert and sslkey types Stanislav Malishevskiy via GitGitGadget
2023-03-20 15:48 ` [PATCH v2] http: add support for " Stanislav Malishevskiy via GitGitGadget
2023-03-20 17:10 ` Jeff King
2023-03-20 18:21 ` Stanislav M
2023-03-21 17:22 ` Jeff King
2023-03-20 17:23 ` Junio C Hamano
2023-03-20 18:24 ` Stanislav M
2023-03-21 17:22 ` Jeff King
2023-03-21 17:43 ` Junio C Hamano [this message]
2023-03-23 9:33 ` Stanislav M
2023-03-23 18:01 ` Jeff King
2023-03-23 18:16 ` Stanislav M
2023-03-29 18:53 ` Junio C Hamano
2023-03-29 19:22 ` Stanislav M
2023-03-29 23:23 ` Jeff King
2023-03-30 0:20 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqjzzahufj.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=peff@peff.net \
--cc=s.malishevskiy@auriga.com \
--cc=stanislav.malishevskiy@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).