From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: jn/experimental-opts-into-proto-v2, was Re: What's cooking in git.git (May 2020, #09; Tue, 26)
Date: Wed, 27 May 2020 14:49:37 -0700 [thread overview]
Message-ID: <xmqq1rn5kpzi.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2005270526280.56@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Wed, 27 May 2020 05:27:54 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Tue, 26 May 2020, Junio C Hamano wrote:
>
>> * jn/experimental-opts-into-proto-v2 (2020-05-21) 1 commit
>> (merged to 'next' on 2020-05-24 at 53cd664dfe)
>> + config: let feature.experimental imply protocol.version=2
>>
>> "feature.experimental" configuration variable is to let volunteers
>> easily opt into a set of newer features, which use of the v2
>> transport protocol is now a part of.
>>
>> Will cook in 'next'.
>
> Given that the `feature.experimental` option is supposed to increase
> testing in the wild, sort of `next` but for users rather than developers
> who build their own Git, could we maybe integrate this into v2.27.0,
> still?
I have been wondering about the same thing, and if it were not using
its own custom way to read the configuration, it would have been a
non-brainer to merge it down before the release. But this late in
the cycle, I'd rather not.
Thanks.
next prev parent reply other threads:[~2020-05-27 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 18:47 What's cooking in git.git (May 2020, #09; Tue, 26) Junio C Hamano
2020-05-27 3:27 ` jn/experimental-opts-into-proto-v2, was " Johannes Schindelin
2020-05-27 21:49 ` Junio C Hamano [this message]
2020-05-27 23:58 ` Jonathan Nieder
2020-05-28 0:43 ` Junio C Hamano
2020-05-27 20:05 ` Johannes Schindelin
2020-05-28 14:44 ` 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=xmqq1rn5kpzi.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).