path: root/Documentation
diff options
authorChristian Couder <>2016-01-24 15:28:16 (GMT)
committerJunio C Hamano <>2016-01-25 20:39:22 (GMT)
commiteaab83d0e574c9f3440a2364a7975f9ffe75f188 (patch)
tree70a71dac844d56516c0a6f3a58c4f9298db38572 /Documentation
parent113e6413187c65a9fbf2b845a1fb31c7d17c0755 (diff)
update-index: add --test-untracked-cache
It is nice to just be able to test if untracked cache is supported without enabling it. Helped-by: David Turner <> Signed-off-by: Christian Couder <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation')
1 files changed, 11 insertions, 1 deletions
diff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt
index f4e5a85..a0afe17 100644
--- a/Documentation/git-update-index.txt
+++ b/Documentation/git-update-index.txt
@@ -18,7 +18,7 @@ SYNOPSIS
- [--[no-|force-]untracked-cache]
+ [--[no-|test-|force-]untracked-cache]
[--really-refresh] [--unresolve] [--again | -g]
[--info-only] [--index-info]
[-z] [--stdin] [--index-version <n>]
@@ -180,6 +180,16 @@ may not support it yet.
system must change `st_mtime` field of a directory if files
are added or deleted in that directory.
+ Only perform tests on the working directory to make sure
+ untracked cache can be used. You have to manually enable
+ untracked cache using `--force-untracked-cache` (or
+ `--untracked-cache` but this will run the tests again)
+ afterwards if you really want to use it. If a test fails
+ the exit code is 1 and a message explains what is not
+ working as needed, otherwise the exit code is 0 and OK is
+ printed.
For safety, `--untracked-cache` performs tests on the working
directory to make sure untracked cache can be used. These