Re: [PATCH v4 0/6] Create 'feature.*' config area and some centralized config parsing

On 8/14/2019 6:32 AM, Derrick Stolee wrote: > On 8/13/2019 5:08 PM, Junio C Hamano wrote: >> Junio C Hamano writes: >> >>> "Derrick Stolee via GitGitGadget" writes: >>> * Update docs and 0 constant in feature.experimental around merge.directoryRenames. >>> >>> I somehow thought that

Re: [PATCH v4 0/6] Create 'feature.*' config area and some centralized config parsing

On 8/13/2019 5:08 PM, Junio C Hamano wrote: > Junio C Hamano writes: > >> "Derrick Stolee via GitGitGadget" writes: >> >>> * Update docs and 0 constant in feature.experimental around >>>merge.directoryRenames. >> >> I somehow thought that the concensus was that *.experimental is for >> thin

Re: [PATCH v4 0/6] Create 'feature.*' config area and some centralized config parsing

Junio C Hamano writes: > "Derrick Stolee via GitGitGadget" writes: > >> * Update docs and 0 constant in feature.experimental around >>merge.directoryRenames. > > I somehow thought that the concensus was that *.experimental is for > things that should become the future default, and this one

Re: [PATCH v4 0/6] Create 'feature.*' config area and some centralized config parsing

"Derrick Stolee via GitGitGadget" writes: > * Update docs and 0 constant in feature.experimental around >merge.directoryRenames. I somehow thought that the concensus was that *.experimental is for things that should become the future default, and this one is not something we would want to m

[PATCH v4 0/6] Create 'feature.*' config area and some centralized config parsing

This is a brand-new thread to replace ds/early-access. The discussion on that thread was very helpful [1]. With this in mind, I propose instead a set of "feature.*" config settings that form groups of "community recommended" settings (with some caveats). In the space below, I'll list a set of poss