Re: [PATCH v2 00/11] More commit-graph/Bloom filter improvements
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 25, 2020, 16:34 UTC
- Message-ID
- <xmqqy2ob3xzq.fsf@gitster.c.googlers.com>
- In-Reply-To
- <4b08360d-04ab-b614-196b-76124f1d54ef@gmail.com>
Derrick Stolee <stolee@gmail.com> writes:
> Question: Should these be GIT_BLOOM_SETTINGS_* instead of GIT_TEST_...? > I ask because this _could_ be a way to allow user customization, > without making it as public as a config option. Or, should I just do > the work and add config settings in this series?
Other than when testing and/or debugging, what are the expected reasons and situations an individual would want to use customized settings? Once a decision is made to use one customized setting for a repository, does it make sense for a setting other than that one setting for the same repository, or is it something very handy if we can use different settings on a whim?
My gut feeling is that it should be added as per-repo configuration but only after a use case is found, and GIT_TEST_* would be the way to go.
Thanks.