Matthieu Moy <matthieu....@grenoble-inp.fr> writes:
> Antoine Pelisse <apeli...@gmail.com> writes:
>>> "git rm" really seems to be a better place for removing files from the
>> 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.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html