On Thu, Nov 01, 2007 at 22:17:11 -0400, Jing Xue wrote: > In the following scenario, why do I have to run 'git reset' following > 'git rm --cached 1.txt' to revert to exactly where I was before 'git add > 1.txt'? Shouldn't 'git rm --cached' have done that already? The message in git-commit suggesting to use 'git rm --cached' to unstage is just plain wrong. It really should mention 'git reset'. git rm, as the name suggests, *removes* the file. git reset, as the name suggests, reverts it to the state it was before (but, somewhat confusingly, with path limit only resets the index, so no --cached option there). -- Jan 'Bulb' Hudec <bulb@xxxxxx>
Attachment:
signature.asc
Description: Digital signature
