From: Jeff King Date: Sun, 9 Dec 2007 08:21:34 +0000 (-0500) Subject: don't mention index refreshing side effect in git-status docs X-Git-Tag: v1.5.4-rc0~33 X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=cc2d6b88f99cb9e00102a509f6069168ff84f08e;p=git.git 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 Signed-off-by: Junio C Hamano --- 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 ------