Re: [PATCH 00/11] [RFC] Create 'core.size=large' setting to update config defaults

From: Derrick Stolee <stolee@gmail.com>
Date: Jun 4, 2019, 14:56 UTC
Message-ID: <6a89e2c3-cbca-176c-1964-7e25d90c0ff7@gmail.com>
In-Reply-To: <nycvar.QRO.7.76.6.1906041641280.1775@tvgsbejvaqbjf.bet>

On 6/4/2019 10:43 AM, Johannes Schindelin wrote:

Show 9 quoted lines

> Hi Stolee,
> 
> On Mon, 3 Jun 2019, Derrick Stolee via GitGitGadget wrote:
> 
>>  1. (Patches 1-3) Introduce a new 'core.size' config setting that takes
>>     'large' as a value. This enables several config values that are
>>     beneficial for large repos.
> 
> I find `core.size` a bit non-descriptive. Maybe `repository.size` instead?

Thanks for the suggestion! If the "repository." doesn't make sense as a top- level category, then maybe "core.repositorySize" would work?

A thought I had overnight that may broaden our options would be to think of this as a tolerance for experimental features. Maybe "core.adoptionRing" with options for "slow" and "fast", where "slow" takes things that have been cooking a long while (index.version=4, core.commitGraph=gc.writeCommitGraph=1) and the "fast" option gets all of those values plus the more experimental options (status.aheadBehind=false, fetch.showForcedUpdates=false).

Alternate names with this slow/fast idea could be:

* core.experimentTolerance={none,low,high}

* core.autoConfig={none,some,all}

Hopefully these options can trigger some creativity to decide on a good name that an experienced Git user could understand.

Thanks, -Stolee