summaryrefslogtreecommitdiff
path: root/Documentation/git-update-index.txt
diff options
context:
space:
mode:
authorÆvar Arnfjörð Bjarmason <avarab@gmail.com>2018-02-09 21:04:31 (GMT)
committerJunio C Hamano <gitster@pobox.com>2018-02-09 21:54:27 (GMT)
commit7bf0be75016058e43181ecc22c65b363beb6d24b (patch)
tree598c59a081a4e68a411402d86e800755c1510d04 /Documentation/git-update-index.txt
parent9b978691b1940024beeccaf8944f7125c746a628 (diff)
downloadgit-7bf0be75016058e43181ecc22c65b363beb6d24b.zip
git-7bf0be75016058e43181ecc22c65b363beb6d24b.tar.gz
git-7bf0be75016058e43181ecc22c65b363beb6d24b.tar.bz2
update-index doc: note the caveat with "could not open..."
Note the caveat where 2.17 is stricter about index validation potentially causing "could not open directory" warnings when git is upgraded. See the preceding "dir.c: stop ignoring opendir() error in open_cached_dir()" change. This caused some mayhem when I upgraded git to a version with this series at Booking.com, and other users have doubtless enabled the UC extension and are in for a surprise when they upgrade. Let's give them a headsup in the docs. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-update-index.txt')
-rw-r--r--Documentation/git-update-index.txt10
1 files changed, 10 insertions, 0 deletions
diff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt
index f0e08d6..b8d3c0d 100644
--- a/Documentation/git-update-index.txt
+++ b/Documentation/git-update-index.txt
@@ -480,6 +480,16 @@ a directory with a file when it comes to the internal structures of
the untracked cache, but no case has been reported where this resulted in
wrong "git status" output.
+There are also cases where existing indexes written by git versions
+before 2.17 will reference directories that don't exist anymore,
+potentially causing many "could not open directory" warnings to be
+printed on "git status". These are new warnings for existing issues
+that were previously silently discarded.
+
+As with the bug described above the solution is to one-off do a "git
+status" run with `core.untrackedCache=false` to flush out the leftover
+bad data.
+
File System Monitor
-------------------