summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Couder <christian.couder@gmail.com>2017-02-27 18:00:06 (GMT)
committerJunio C Hamano <gitster@pobox.com>2017-03-01 21:24:22 (GMT)
commit13c0e4c4782976fbda24fdde31d67ef29f41cb34 (patch)
tree61be535f7172a242798b93ee5baa3f4f52cfdaa1
parent66f9e7a6e83e01358bc5b96c5f7f1e5b9b718779 (diff)
downloadgit-13c0e4c4782976fbda24fdde31d67ef29f41cb34.zip
git-13c0e4c4782976fbda24fdde31d67ef29f41cb34.tar.gz
git-13c0e4c4782976fbda24fdde31d67ef29f41cb34.tar.bz2
Documentation/git-update-index: talk about core.splitIndex config var
Signed-off-by: Christian Couder <chriscool@tuxfamily.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-update-index.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt
index 7386c93..e091b2a 100644
--- a/Documentation/git-update-index.txt
+++ b/Documentation/git-update-index.txt
@@ -171,6 +171,12 @@ may not support it yet.
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.
++
+These options take effect whatever the value of the `core.splitIndex`
+configuration variable (see linkgit:git-config[1]). But a warning is
+emitted when the change goes against the configured value, as the
+configured value will take effect next time the index is read and this
+will remove the intended effect of the option.
--untracked-cache::
--no-untracked-cache::