From: Daniel Stenberg <daniel@haxx.se>
To: "Force.Charlie-I via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 0/1] http: add support selecting http version
Date: Wed, 7 Nov 2018 14:44:51 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1811071443130.3368@tvnag.unkk.fr> (raw)
In-Reply-To: <pull.69.git.gitgitgadget@gmail.com>
On Wed, 7 Nov 2018, Force.Charlie-I via GitGitGadget wrote:
> Normally, git doesn't need to set curl to select the HTTP version, it works
> fine without HTTP2. Adding HTTP2 support is a icing on the cake.
Just a FYI:
Starting with libcurl 7.62.0 (released a week ago), it now defaults to the
"2TLS" setting unless you tell it otherwise. With 2TLS, libcurl will attempt
to use HTTP/2 for HTTPS URLs.
--
/ daniel.haxx.se
next prev parent reply other threads:[~2018-11-07 13:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 13:33 [PATCH 0/1] http: add support selecting http version Force.Charlie-I via GitGitGadget
2018-11-07 13:33 ` [PATCH 1/1] " Force Charlie via GitGitGadget
2018-11-08 1:48 ` Junio C Hamano
2018-11-07 13:44 ` Daniel Stenberg [this message]
2018-11-08 1:18 ` [PATCH 0/1] " brian m. carlson
2018-11-08 3:35 ` Junio C Hamano
2018-11-08 1:35 ` [PATCH v2 0/3] " Force.Charlie-I via GitGitGadget
2018-11-08 1:35 ` [PATCH v2 1/3] " Force Charlie via GitGitGadget
2018-11-08 1:35 ` [PATCH v2 2/3] support force use http 1.1 Force Charlie via GitGitGadget
2018-11-08 1:35 ` [PATCH v2 3/3] fix curl version to support CURL_HTTP_VERSION_2TLS Force Charlie via GitGitGadget
2018-11-08 4:54 ` [PATCH v3 0/4] http: add support selecting http version Force.Charlie-I via GitGitGadget
2018-11-08 4:54 ` [PATCH v3 1/4] " Force Charlie via GitGitGadget
2018-11-08 4:55 ` [PATCH v3 2/4] support force use http 1.1 Force Charlie via GitGitGadget
2018-11-08 4:55 ` [PATCH v3 3/4] fix curl version to support CURL_HTTP_VERSION_2TLS Force Charlie via GitGitGadget
2018-11-08 4:55 ` [PATCH v3 4/4] http: change http.version value type Force Charlie via GitGitGadget
2018-11-08 6:14 ` [PATCH v4 0/4] http: add support selecting http version Force.Charlie-I via GitGitGadget
2018-11-08 6:14 ` [PATCH v4 1/4] " Force Charlie via GitGitGadget
2018-11-08 6:14 ` [PATCH v4 2/4] support force use http 1.1 Force Charlie via GitGitGadget
2018-11-08 6:14 ` [PATCH v4 3/4] fix curl version to support CURL_HTTP_VERSION_2TLS Force Charlie via GitGitGadget
2018-11-08 6:14 ` [PATCH v4 4/4] http: change http.version value type Force Charlie via GitGitGadget
2018-11-08 6:18 ` [PATCH v5 0/1] http: add support selecting http version Force.Charlie-I via GitGitGadget
2018-11-08 6:18 ` [PATCH v5 1/1] " Force Charlie via GitGitGadget
2018-11-08 7:00 ` [PATCH v6 0/1] " Force.Charlie-I via GitGitGadget
2018-11-08 7:00 ` [PATCH v6 1/1] " Force Charlie via GitGitGadget
2018-11-08 18:02 ` Eric Sunshine
2018-11-09 2:57 ` Junio C Hamano
2018-11-09 2:56 ` Junio C Hamano
2018-11-08 23:15 ` [PATCH v7 0/1] " Force.Charlie-I via GitGitGadget
2018-11-08 23:15 ` [PATCH v7 1/1] " Force Charlie via GitGitGadget
2018-11-09 3:52 ` Junio C Hamano
2018-11-09 3:44 ` [PATCH v8 0/1] " Force.Charlie-I via GitGitGadget
2018-11-09 3:44 ` [PATCH v8 1/1] " Force Charlie via GitGitGadget
2018-11-08 6:14 ` [PATCH v3 0/4] " 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=alpine.DEB.2.20.1811071443130.3368@tvnag.unkk.fr \
--to=daniel@haxx.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.