[PATCH v2 0/3] http: add support selecting http version

2018-11-07 Thread Force.Charlie-I via GitGitGadget
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. When http.version=20 is set, git will attempt to request the server using HTTP2. If the remote server does not support HTTP2, it is no different. Currently

[PATCH v3 0/4] http: add support selecting http version

2018-11-07 Thread Force.Charlie-I via GitGitGadget
Normally, git doesn't need to set curl to select the HTTP version, it works fine without HTTP/2. Adding HTTP/2 support is a icing on the cake. This patch support force enable HTTP/2 or HTTP/1.1. example: GIT_CURL_VERBOSE=1 git2 -c http.version=HTTP/2 ls-remote

[PATCH v4 0/4] http: add support selecting http version

2018-11-07 Thread Force.Charlie-I via GitGitGadget
Normally, git doesn't need to set curl to select the HTTP version, it works fine without HTTP/2. Adding HTTP/2 support is a icing on the cake. This patch support force enable HTTP/2 or HTTP/1.1. example: GIT_CURL_VERBOSE=1 git2 -c http.version=HTTP/2 ls-remote

[PATCH v5 0/1] http: add support selecting http version

2018-11-07 Thread Force.Charlie-I via GitGitGadget
Normally, git doesn't need to set curl to select the HTTP version, it works fine without HTTP/2. Adding HTTP/2 support is a icing on the cake. This patch support force enable HTTP/2 or HTTP/1.1. example: GIT_CURL_VERBOSE=1 git2 -c http.version=HTTP/2 ls-remote

[PATCH v6 0/1] http: add support selecting http version

2018-11-07 Thread Force.Charlie-I via GitGitGadget
Usually we don't need to set libcurl to choose which version of the HTTP protocol to use to communicate with a server. But different versions of libcurl, the default value is not the same. CURL >= 7.62.0: CURL_HTTP_VERSION_2TLS CURL < 7.62: CURL_HTTP_VERSION_1_1 In order to give users the

[PATCH v7 0/1] http: add support selecting http version

2018-11-08 Thread Force.Charlie-I via GitGitGadget
Usually we don't need to set libcurl to choose which version of the HTTP protocol to use to communicate with a server. But different versions of libcurl, the default value is not the same. CURL >= 7.62.0: CURL_HTTP_VERSION_2TLS CURL < 7.62: CURL_HTTP_VERSION_1_1 In order to give users the

[PATCH v8 0/1] http: add support selecting http version

2018-11-08 Thread Force.Charlie-I via GitGitGadget
Usually we don't need to set libcurl to choose which version of the HTTP protocol to use to communicate with a server. But different versions of libcurl, the default value is not the same. CURL >= 7.62.0: CURL_HTTP_VERSION_2TLS CURL < 7.62: CURL_HTTP_VERSION_1_1 In order to give users the

[PATCH 0/1] http: add support selecting http version

2018-11-07 Thread Force.Charlie-I via GitGitGadget
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. When http.version=20 is set, git will attempt to request the server using HTTP2. If the remote server does not support HTTP2, it is no different. Currently