git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Git List <git@vger.kernel.org>
Subject: Re: js/mingw-http-ssl, was Re: What's cooking in git.git (Oct 2018, #05; Fri, 26)
Date: Tue, 30 Oct 2018 14:37:39 +0900	[thread overview]
Message-ID: <xmqqtvl40zbw.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAPig+cTJR4Qhqf_VVCihNW91tGt8Mbi2Oy99jzg8NmAksKoXVA@mail.gmail.com> (Eric Sunshine's message of "Mon, 29 Oct 2018 22:22:12 -0400")

Eric Sunshine <sunshine@sunshineco.com> writes:

> On Mon, Oct 29, 2018 at 10:10 PM Junio C Hamano <gitster@pobox.com> wrote:
>> How's this?
>>
>>     On platforms with recent cURL library, http.sslBackend configuration
>>     variable can be used to choose different SSL backend at runtime.
>
> s/choose/& a/
>
>>     The Windows port uses this mechanism to switch between OpenSSL and
>>     Secure Channel while talking over the HTTPS protocol.

Thanks.

By the way, I am beginning to like this phrasing quite a lot.  It
encourages those with other ports like Linux and Mac to see if they
want a similar runtime switching by singling out Windows port, which
was what I wanted to achive with the original one, but I think the
updated text does so more effectively.

  reply	other threads:[~2018-10-30  5:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26  7:57 What's cooking in git.git (Oct 2018, #05; Fri, 26) Junio C Hamano
2018-10-26 12:09 ` js/mingw-http-ssl, was " Johannes Schindelin
2018-10-26 13:19   ` Junio C Hamano
2018-10-29 13:22     ` Johannes Schindelin
2018-10-30  2:09       ` Junio C Hamano
2018-10-30  2:22         ` Eric Sunshine
2018-10-30  5:37           ` Junio C Hamano [this message]
2018-10-30  5:49             ` Kaartic Sivaraam
2018-10-30 10:16             ` Johannes Schindelin
2018-10-26 19:04 ` Stefan Beller
2018-10-27  7:29   ` Junio C Hamano
2018-10-27  3:45 ` Taylor Blau
2018-10-27  6:27   ` 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=xmqqtvl40zbw.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=sunshine@sunshineco.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;
as well as URLs for NNTP newsgroup(s).