Re: [PATCH 2/2] git-rm doc: Describe how to sync index & work tree

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 7, 2009, 21:08 UTC
Message-ID: <7vpr6qze4i.fsf@alter.siamese.dyndns.org>
In-Reply-To: <4B1D4AFE.6090708@gmail.com>

Looks sensible.

I think mentioning "add -u" in the same section as "commit -a" would be helpful, as these two are more for user's own development (as opposed to vendor-code-drop). I'd perhaps squash something like this in. Please say "yes", "don't, it is horrible", or something in between ;-)

--
 Documentation/git-rm.txt |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/Documentation/git-rm.txt b/Documentation/git-rm.txt
index c622972..42161d7 100644
--- a/Documentation/git-rm.txt
+++ b/Documentation/git-rm.txt
@@ -94,7 +94,8 @@ If you intend that your next commit should record all modifications
 of tracked files in the working tree and record all removals of
 files that have been removed from the working tree with `rm`
 (as opposed to `git rm`), use `git commit -a`, as it will
-automatically notice and record all removals.
+automatically notice and record all removals.  `git add -u`
+can be used for a similar effect without commiting.
 
 Using "git add -A"
 ~~~~~~~~~~~~~~~~~~