From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 08 Aug 2019 20:07:48 GMT
Subject: Re: [PATCH v3 5/5] repo-settings: create feature.experimental setting
Message-ID: <xmqqv9v7e7zf.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <CABPp-BH2EHGEmOj3kpeTMV2PpKkRBpPn3FuBfNDHKA8=BkKxFQ@mail.gmail.com>

Elijah Newren <newren@gmail.com> writes:

> However, Stollee's commit message started with "The
> 'feature.experimental' setting includes config options that are not
> committed to become defaults".
>
> If these are settings that are "intended" but not "committed" to
> become defaults, then yes, you're absolutely right.  (And in such a
> case, it might be nice to add that distinction to the commit message.)

My understanding is that the only purpose of feature.experimental
is: "we want to change the default of X this way, but we do not know
if we missed an important use case that would be harmed by such a
change, so let's see if those who volunteered to be guinea pigs by
setting feature.experimental to true find glitches in our thinking
that led us to think the change of the default is a good idea".