git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v1 19/19] Documentation/git-update-index: explain splitIndex.*

From
Christian Couder <christian.couder@gmail.com>
Date
Oct 23, 2016, 09:26 UTC
Message-ID
<20161023092648.12086-20-chriscool@tuxfamily.org>
In-Reply-To
<20161023092648.12086-1-chriscool@tuxfamily.org>
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
 Documentation/git-update-index.txt | 33 +++++++++++++++++++++++++--------
 1 file changed, 25 insertions(+), 8 deletions(-)
diff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt
index e091b2a..635d157 100644
--- a/Documentation/git-update-index.txt
+++ b/Documentation/git-update-index.txt
@@ -163,14 +163,10 @@ may not support it yet.
 
 --split-index::
 --no-split-index::
-	Enable or disable split index mode. If enabled, the index is
-	split into two files, $GIT_DIR/index and $GIT_DIR/sharedindex.<SHA-1>.
-	Changes are accumulated in $GIT_DIR/index while the shared
-	index file contains all index entries stays unchanged. If
-	split-index mode is already enabled and `--split-index` is
-	given again, all changes in $GIT_DIR/index are pushed back to
-	the shared index file. This mode is designed for very large
-	indexes that take a significant amount of time to read or write.
+	Enable or disable split index mode. If split-index mode is
+	already enabled and `--split-index` is given again, all
+	changes in $GIT_DIR/index are pushed back to the shared index
+	file.
 +
 These options take effect whatever the value of the `core.splitIndex`
 configuration variable (see linkgit:git-config[1]). But a warning is
@@ -394,6 +390,27 @@ Although this bit looks similar to assume-unchanged bit, its goal is
 different from assume-unchanged bit's. Skip-worktree also takes
 precedence over assume-unchanged bit when both are set.
 
+Split index
+-----------
+
+This mode is designed for very large indexes that take a significant
+amount of time to read or write.
+
+In this mode, the index is split into two files, $GIT_DIR/index and
+$GIT_DIR/sharedindex.<SHA-1>. Changes are accumulated in
+$GIT_DIR/index, the split index, while the shared index file contains
+all index entries and stays unchanged.
+
+All changes in the split index are pushed back to the shared index
+file when the number of entries in the split index reaches a level
+specified by the splitIndex.maxPercentChange config variable (see
+linkgit:git-config[1]).
+
+Each time a new shared index file is created, the old shared index
+files are deleted if they are older than what is specified by the
+splitIndex.sharedIndexExpire config variable (see
+linkgit:git-config[1]).
+
 Untracked cache
 ---------------
 
-- 
2.10.1.462.g7e1e03a
Previous: Christian CouderNext: Christian Couder
Message 43 of 66 in “Add configuration options for split-index”
  1. 00/19 Add configuration options for split-indexChristian Couder, Oct 23, 2016
  2. 02/19 config: add git_config_get_split_index()Christian Couder, Oct 23, 2016
  3. 05/19 update-index: warn in case of split-index incoherencyChristian Couder, Oct 23, 2016
  4. Duy NguyenOct 25, 2016
  5. Christian CouderOct 29, 2016
  6. Junio C HamanoNov 1, 2016
  7. Christian CouderNov 1, 2016
  8. Junio C HamanoNov 2, 2016
  9. 04/19 read-cache: add and then use tweak_split_index()Christian Couder, Oct 23, 2016
  10. 01/19 split-index: s/eith/with/ typo fixChristian Couder, Oct 23, 2016
  11. 03/19 split-index: add {add,remove}_split_index() functionsChristian Couder, Oct 23, 2016
  12. Duy NguyenOct 25, 2016
  13. Christian CouderOct 29, 2016
  14. Duy NguyenNov 7, 2016
  15. Duy NguyenNov 9, 2016
  16. Christian CouderNov 9, 2016
  17. 07/19 Documentation/config: add information for core.splitIndexChristian Couder, Oct 23, 2016
  18. 09/19 config: add git_config_get_max_percent_split_change()Christian Couder, Oct 23, 2016
  19. Duy NguyenOct 25, 2016
  20. Christian CouderOct 29, 2016
  21. Junio C HamanoNov 1, 2016
  22. Christian CouderNov 5, 2016
  23. 13/19 sha1_file: make check_and_freshen_file() non staticChristian Couder, Oct 23, 2016
  24. 12/19 Documentation/config: add splitIndex.maxPercentChangeChristian Couder, Oct 23, 2016
  25. Junio C HamanoNov 1, 2016
  26. Christian CouderNov 5, 2016
  27. Junio C HamanoNov 6, 2016
  28. 11/19 t1700: add tests for splitIndex.maxPercentChangeChristian Couder, Oct 23, 2016
  29. Junio C HamanoNov 1, 2016
  30. 10/19 read-cache: regenerate shared index if necessaryChristian Couder, Oct 23, 2016
  31. Ramsay JonesOct 23, 2016
  32. Christian CouderOct 29, 2016
  33. Duy NguyenOct 25, 2016
  34. Christian CouderOct 29, 2016
  35. 15/19 config: add git_config_get_date_string() from gc.cChristian Couder, Oct 23, 2016
  36. Junio C HamanoNov 1, 2016
  37. Christian CouderNov 23, 2016
  38. Junio C HamanoNov 23, 2016
  39. Christian CouderNov 28, 2016
  40. Junio C HamanoNov 28, 2016
  41. 17/19 t1700: test shared index file expirationChristian Couder, Oct 23, 2016
  42. 18/19 Documentation/config: add splitIndex.sharedIndexExpireChristian Couder, Oct 23, 2016
  43. 19/19 Documentation/git-update-index: explain splitIndex.*Christian Couder, Oct 23, 2016
  44. 16/19 read-cache: unlink old sharedindex filesChristian Couder, Oct 23, 2016
  45. Duy NguyenOct 25, 2016
  46. Duy NguyenOct 27, 2016
  47. Christian CouderOct 27, 2016
  48. Junio C HamanoOct 27, 2016
  49. Duy NguyenOct 29, 2016
  50. 08/19 Documentation/git-update-index: talk about core.splitIndex config varChristian Couder, Oct 23, 2016
  51. 14/19 read-cache: touch shared index files when usedChristian Couder, Oct 23, 2016
  52. Duy NguyenOct 25, 2016
  53. Junio C HamanoNov 1, 2016
  54. 06/19 t1700: add tests for core.splitIndexChristian Couder, Oct 23, 2016
  55. Junio C HamanoOct 24, 2016
  56. Duy NguyenOct 25, 2016
  57. Junio C HamanoOct 25, 2016
  58. Duy NguyenOct 26, 2016
  59. Junio C HamanoOct 26, 2016
  60. Duy NguyenOct 25, 2016
  61. Christian CouderNov 3, 2016
  62. Duy NguyenNov 7, 2016
  63. Christian CouderNov 18, 2016
  64. Duy NguyenNov 22, 2016
  65. Christian CouderNov 22, 2016
  66. Duy NguyenNov 22, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.