Thread (1 message) 1 message, 1 author, 2016-06-15
  • (off-list ancestor, not in this archive)
  • Re: [RFC] git rm -u · Junio C Hamano <hidden> · 2016-06-15

Re: [RFC] git rm -u

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

Matthieu Moy [off-list ref] writes:
Antoine Pelisse [off-list ref] writes:
quoted
quoted
"git rm" really seems to be a better place for removing files from the
index.
Then, I don't exactly understand the meaning of git-rm but being a
_shortcut_ for "remove and stage".
"git rm --cached" is exactly "remove from index".

And even without --cached, as you notice yourself, it does a "remove and
stage [removal]", so why would it be inappropriate to stage a removal?
I do not think "git rm" is a bad place to add the feature; I was
questioning if "-u" is an appropriate option.  The option "-u" given
to "git add" is internally called "take worktree changes", and we
would need the option to "git rm" with that internal meaning.  The
superficial meaning "updated" that "-u" in "add -u" stands for does
not really match what "git rm --take-worktree-changes" wants to do,
as we obviously do not want to remove all updated/modified files.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help