aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2007-12-09 03:21:34 -0500
committerJunio C Hamano <gitster@pobox.com>2007-12-09 02:39:53 -0800
commitcc2d6b88f99cb9e00102a509f6069168ff84f08e (patch)
tree3052cd54c415120e0196a2e53977cf97f397ed0b
parentbb4e3527b5d59a2db406dfa6519927a97d61770d (diff)
downloadgit-cc2d6b88f99cb9e00102a509f6069168ff84f08e.tar.gz
git-cc2d6b88f99cb9e00102a509f6069168ff84f08e.tar.xz
don't mention index refreshing side effect in git-status docs
The tip about speeding up subsequent operations is now obsolete; since aecbf914, git-diff now squelches empty diffs and performs an automatic refresh. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-status.txt7
1 files changed, 0 insertions, 7 deletions
diff --git a/Documentation/git-status.txt b/Documentation/git-status.txt
index a1bb9bd82..5c5a480ec 100644
--- a/Documentation/git-status.txt
+++ b/Documentation/git-status.txt
@@ -28,13 +28,6 @@ If there is no path that is different between the index file and
the current HEAD commit (i.e., there is nothing to commit by running
`git-commit`), the command exits with non-zero status.
-If any paths have been touched in the working tree (that is,
-their modification times have changed) but their contents and
-permissions are identical to those in the index file, the command
-updates the index file. Running `git-status` can thus speed up
-subsequent operations such as `git-diff` if the working tree
-contains many paths that have been touched but not modified.
-
OUTPUT
------