Christian Couder <christian.couder@xxxxxxxxx> writes: > Signed-off-by: Christian Couder <chriscool@xxxxxxxxxxxxx> > --- > Documentation/config.txt | 13 +++++++++++++ > 1 file changed, 13 insertions(+) > > diff --git a/Documentation/config.txt b/Documentation/config.txt > index 96521a4..380eeb8 100644 > --- a/Documentation/config.txt > +++ b/Documentation/config.txt > @@ -2763,6 +2763,19 @@ showbranch.default:: > The default set of branches for linkgit:git-show-branch[1]. > See linkgit:git-show-branch[1]. > > +splitIndex.maxPercentChange:: > + When the split index feature is used, this specifies the > + percent of entries the split index can contain compared to the > + whole number of entries in both the split index and the shared > + index before a new shared index is written. > + The value should be between 0 and 100. If the value is 0 then > + a new shared index is always written, if it is 100 a new > + shared index is never written. Hmph. The early part of the description implies this will kick in only when some other conditions (i.e. the bit in the index or the other configuration) are met, but if this disables the split index when it is set to 0, would we even need the other configuration variable? IOW, perhaps we can do without core.splitIndex? > + By default the value is 20, so a new shared index is written > + if the number of entries in the split index would be greater > + than 20 percent of the total number of entries. > + See linkgit:git-update-index[1].