
I was just committing changes, neatly splitting them up into several commits when I made a mistake (I committed one file too much). So I thought I'd strip that last commit even though I still had uncommitted changes. Don't do that! All your uncommitted changes will be gone too, not only the commit you stripped. :-(
By the way, does someone know the proper way to do this - without loosing all uncommitted changes?
I think in this very special case you could have used rollback which undoes the last commit iff there have not yet been any other hg operations since it was created.

Another way would use the shelve feature to move uncommitted changes out of the way temporarily.
Also, your uncommitted changes might be in a backup folder somewhere in the .hg directory.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill