Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
fsmonitor: update documentation to remove reference to invalid config settings
author
Ben Peart
<benpeart@microsoft.com>
Wed, 14 Feb 2018 15:41:30 +0000
(10:41 -0500)
committer
Junio C Hamano
<gitster@pobox.com>
Wed, 14 Feb 2018 18:27:26 +0000
(10:27 -0800)
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>
Documentation/git-update-index.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
b4f61b7
)
diff --git
a/Documentation/git-update-index.txt
b/Documentation/git-update-index.txt
index 7c2f880a222e840c4c61cc57460e2b9a6a0a37a2..2fec666ee39f78e103f3ed67bd89315394f90399 100644
(file)
--- 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
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
When the `core.fsmonitor` configuration variable is changed, the
file system monitor is added to or removed from the index the next time