From: Junio C Hamano <gitster@pobox.com>
To: "Björn Gustavsson" <bgustavsson@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] git-rm doc: Describe how to sync index & work tree
Date: Mon, 07 Dec 2009 13:08:13 -0800 [thread overview]
Message-ID: <7vpr6qze4i.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4B1D4AFE.6090708@gmail.com> ("Björn Gustavsson"'s message of "Mon\, 07 Dec 2009 19\:35\:42 +0100")
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"
~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2009-12-07 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 18:35 [PATCH 2/2] git-rm doc: Describe how to sync index & work tree Björn Gustavsson
2009-12-07 21:08 ` Junio C Hamano [this message]
2009-12-08 6:12 ` Björn Gustavsson
2009-12-08 6:19 ` Björn Gustavsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vpr6qze4i.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bgustavsson@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox