It seems logical to me that git-reset <>'s 
--hard option resets everything, what's staged, what's not, etc. I see it 
as a *"make my working dir in the exact same state as this commit"* 
command, which I believe it is. If you don't want it to reset your index or 
working dir or both, see git-reset <>'s 
other modes.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to