Re: [PATCH v3 14/14] builtin/commit-graph.c: introduce '--max-new-filters=<n>'
- From
SZEDER Gábor <szeder.dev@gmail.com>
- Date
- Aug 19, 2020, 08:20 UTC
- Message-ID
- <20200819082021.GA5238@szeder.dev>
- In-Reply-To
- <09f6871f66bff838c067a3e0d23cd4622171f3bd.1597178915.git.me@ttaylorr.com>
On Tue, Aug 11, 2020 at 04:52:14PM -0400, Taylor Blau wrote:
Show 9 quoted lines
> Introduce a command-line flag and configuration variable to fill in the > 'max_new_filters' variable introduced by the previous patch. > > The command-line option '--max-new-filters' takes precedence over > 'commitGraph.maxNewFilters', which is the default value. > '--no-max-new-filters' can also be provided, which sets the value back > to '-1', indicating that an unlimited number of new Bloom filters may be > generated. (OPT_INTEGER only allows setting the '--no-' variant back to > '0', hence a custom callback was used instead).
Forgot the most important thing: Why? Please explain in the commit message why this option is necesary, what problems does it solve, how it is supposed to interact with other options and why so.