summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Peart <benpeart@microsoft.com>2018-02-14 10:41:30 -0500
committerJunio C Hamano <gitster@pobox.com>2018-02-14 10:27:26 -0800
commit4ccf461f56158b46e86731b0040e412e60b95a6e (patch)
treea5ad87e6cce6f739a451a747d2c01f0f21adcad5
parentb4f61b7fa455b6bea2a12d46c59d8685f761018b (diff)
downloadgit-4ccf461f56158b46e86731b0040e412e60b95a6e.tar.gz
fsmonitor: update documentation to remove reference to invalid config settingsbp/fsmonitor
Remove the reference to setting core.fsmonitor to `true` (or `false`) as those are not valid settings. Signed-off-by: Ben Peart <benpeart@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-update-index.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt
index 7c2f880a22..2fec666ee3 100644
--- a/Documentation/git-update-index.txt
+++ b/Documentation/git-update-index.txt
@@ -484,8 +484,8 @@ the `core.fsmonitor` configuration variable (see
linkgit:git-config[1]) than using the `--fsmonitor` option to
`git update-index` in each repository, especially if you want to do so
across all repositories you use, because you can set the configuration
-variable to `true` (or `false`) in your `$HOME/.gitconfig` just once
-and have it affect all repositories you touch.
+variable in your `$HOME/.gitconfig` just once and have it affect all
+repositories you touch.
When the `core.fsmonitor` configuration variable is changed, the
file system monitor is added to or removed from the index the next time