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

Subsystems: documentation, the rest

3 messages, 2 authors, 2016-06-15 · open the first message on its own page

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

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:47:51

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"
 ~~~~~~~~~~~~~~~~~~

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

From: Björn Gustavsson <hidden>
Date: 2016-06-15 22:47:51

2009/12/7 Junio C Hamano [off-list ref]:
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 ;-)
Yes. :-)

-- 
Björn Gustavsson, Erlang/OTP, Ericsson AB

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

From: Björn Gustavsson <hidden>
Date: 2016-06-15 22:47:51

2009/12/7 Junio C Hamano [off-list ref]:
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 ;-)
Yes, but...
-automatically notice and record all removals.
+automatically notice and record all removals.  `git add -u`
+can be used for a similar effect without commiting.
s/commiting/committing/

-- 
Björn Gustavsson, Erlang/OTP, Ericsson AB
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help