From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>,
Jonathan Tan <jonathantanmy@google.com>
Subject: Re: [PATCH] protocol: re-enable v2 protocol by default
Date: Fri, 25 Sep 2020 11:41:08 -0700 [thread overview]
Message-ID: <xmqq4knllmwr.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200925183436.GA659633@coredump.intra.peff.net> (Jeff King's message of "Fri, 25 Sep 2020 14:34:36 -0400")
Jeff King <peff@peff.net> writes:
> Let's move forward with v2 as the default again. It's possible there are
> still lurking bugs, but we won't know until it gets more widespread use.
> And we can find and squash them just like any other bug at this point.
Ack. Thanks.
>
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> After seeing yet another round of "if you use the v2 protocol, all of
> your issues fetching a non-tip object for submodules or CI will go away"
> advice today, I was reminded that we haven't picked up the question
> again of when we should look at v2 becoming the default again.
>
> Documentation/config/feature.txt | 4 ----
> Documentation/config/protocol.txt | 3 +--
> protocol.c | 6 +-----
> 3 files changed, 2 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/config/feature.txt b/Documentation/config/feature.txt
> index c0cbf2bb1c..cdecd04e5b 100644
> --- a/Documentation/config/feature.txt
> +++ b/Documentation/config/feature.txt
> @@ -14,10 +14,6 @@ feature.experimental::
> +
> * `fetch.negotiationAlgorithm=skipping` may improve fetch negotiation times by
> skipping more commits at a time, reducing the number of round trips.
> -+
> -* `protocol.version=2` speeds up fetches from repositories with many refs by
> -allowing the client to specify which refs to list before the server lists
> -them.
>
> feature.manyFiles::
> Enable config options that optimize for repos with many files in the
> diff --git a/Documentation/config/protocol.txt b/Documentation/config/protocol.txt
> index c46e9b3d00..756591d77b 100644
> --- a/Documentation/config/protocol.txt
> +++ b/Documentation/config/protocol.txt
> @@ -48,8 +48,7 @@ protocol.version::
> If set, clients will attempt to communicate with a server
> using the specified protocol version. If the server does
> not support it, communication falls back to version 0.
> - If unset, the default is `0`, unless `feature.experimental`
> - is enabled, in which case the default is `2`.
> + If unset, the default is `2`.
> Supported versions:
> +
> --
> diff --git a/protocol.c b/protocol.c
> index 8d964fc65e..052d7edbb9 100644
> --- a/protocol.c
> +++ b/protocol.c
> @@ -17,7 +17,6 @@ static enum protocol_version parse_protocol_version(const char *value)
> enum protocol_version get_protocol_version_config(void)
> {
> const char *value;
> - int val;
> const char *git_test_k = "GIT_TEST_PROTOCOL_VERSION";
> const char *git_test_v;
>
> @@ -31,9 +30,6 @@ enum protocol_version get_protocol_version_config(void)
> return version;
> }
>
> - if (!git_config_get_bool("feature.experimental", &val) && val)
> - return protocol_v2;
> -
> git_test_v = getenv(git_test_k);
> if (git_test_v && *git_test_v) {
> enum protocol_version env = parse_protocol_version(git_test_v);
> @@ -43,7 +39,7 @@ enum protocol_version get_protocol_version_config(void)
> return env;
> }
>
> - return protocol_v0;
> + return protocol_v2;
> }
>
> enum protocol_version determine_protocol_version_server(void)
next prev parent reply other threads:[~2020-09-25 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 18:34 [PATCH] protocol: re-enable v2 protocol by default Jeff King
2020-09-25 18:41 ` Junio C Hamano [this message]
2020-09-25 21:24 ` jrnieder
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=xmqq4knllmwr.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/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).