Re: jn/experimental-opts-into-proto-v2, was Re: What's cooking in git.git (May 2020, #09; Tue, 26)

From: Junio C Hamano <gitster@pobox.com>
Date: May 27, 2020, 21:49 UTC
Message-ID: <xmqq1rn5kpzi.fsf@gitster.c.googlers.com>
In-Reply-To: <nycvar.QRO.7.76.6.2005270526280.56@tvgsbejvaqbjf.bet>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 16 quoted lines

> 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.