Re: Recommended configurations (was Re: [PATCH v1 2/2] reset: add new reset.quietDefault config setting)

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 25, 2018, 04:09 UTC
Message-ID: <xmqqd0rylla8.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20181024235813.GA1399@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

> I do hope that some options will just be no-brainers to enable always,
> though (e.g., I think in the long run commit-graph should just default
> to "on"; it's cheap to keep up to date and helps proportionally to the
> repo size).

Same here.

We should strive to make any feature to optimize for repositories with a particular trait not to hurt too much to repositories without that trait, so that we can start such a feature as opt-in but later can make it the default for everybody. Sometimes it may not be possible, but my gut feeling is that features aiming for optimizing big repositories should fundamentally need only very small overhead when enabled in a small repository.

So I view them not as a set of million "if your repository matches this criterion, turn it on" knobs. Rather, they are "we haven't tested it fully, but you can opt into the experiment a new way to do the same operation, which is designed to optimize for repositories with this trait. Enabling it even when your repository does not have that trait and reporting regression is also very welcome, as it is a good indication that the new way has rough edges at its corners".

Thanks.