Skip to content

Commit

Permalink
doc: core.ignoreStat clarify the --assume-unchanged effect
Browse files Browse the repository at this point in the history
The assume-unchanged bit can be misunderstood. Be assertive about
the expectation that file changes should update that flag.

Signed-off-by: Philip Oakley <philipoakley@iee.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
  • Loading branch information
Philip Oakley authored and Junio C Hamano committed Dec 12, 2014
1 parent 9abc44b commit 1be976e
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions Documentation/config.txt
Original file line number Diff line number Diff line change
Expand Up @@ -366,10 +366,11 @@ proxy use, while defaulting to a common proxy for external domains.
core.ignoreStat::
If true, commands which modify both the working tree and the index
will mark the updated paths with the "assume unchanged" bit in the
index. These marked files are then assumed to stay unchanged in the
working tree, until you mark them otherwise manually - Git will not
detect the file changes by lstat() calls. This is useful on systems
where those are very slow, such as Microsoft Windows.
index. These marked files are then expected to stay unchanged in the
working tree. If you change them you should mark their update manually.
Git will normally not detect the file changes by lstat() calls.
This is useful on systems where those calls are very slow, such as
cifs/Microsoft Windows.
See linkgit:git-update-index[1].
False by default.

Expand Down

0 comments on commit 1be976e

Please sign in to comment.