]>
Commit | Line | Data |
---|---|---|
2ef0e469 NTND |
1 | splitIndex.maxPercentChange:: |
2 | When the split index feature is used, this specifies the | |
3 | percent of entries the split index can contain compared to the | |
4 | total number of entries in both the split index and the shared | |
5 | index before a new shared index is written. | |
4d542687 EN |
6 | The value should be between 0 and 100. If the value is 0, then |
7 | a new shared index is always written; if it is 100, a new | |
2ef0e469 | 8 | shared index is never written. |
4d542687 | 9 | By default, the value is 20, so a new shared index is written |
2ef0e469 NTND |
10 | if the number of entries in the split index would be greater |
11 | than 20 percent of the total number of entries. | |
12 | See linkgit:git-update-index[1]. | |
13 | ||
14 | splitIndex.sharedIndexExpire:: | |
15 | When the split index feature is used, shared index files that | |
16 | were not modified since the time this variable specifies will | |
17 | be removed when a new shared index file is created. The value | |
18 | "now" expires all entries immediately, and "never" suppresses | |
19 | expiration altogether. | |
20 | The default value is "2.weeks.ago". | |
21 | Note that a shared index file is considered modified (for the | |
22 | purpose of expiration) each time a new split-index file is | |
23 | either created based on it or read from it. | |
24 | See linkgit:git-update-index[1]. |