Hg rollback at the command line should revert the commit but not the changes (I don't use tortoisehg, so unclear if it puts that in a nice UI).
Looks like it does, through the Recovery dialog. Will try this next time such a thing happens (pretty soon). – Maxim Zaslavsky Jun 27 '10 at 4:22 Also, is it possible to somehow go back now and get rid of the faulty commits (and thus, the merges, too)?
– Maxim Zaslavsky Jun 27 '10 at 4:27 2 Don't focus too much on that - they're not "faulty" so much as just a recording of what happened. You should banish from your mind the thought of ever trying to "fix" history in a revision control system - history already happened, it's immutable. (The only time you ever want to risk really bad things in order to change history is if you committed nuclear launch codes into your RCS by mistake).
– Nick Bastin Jun 27 '10 at 4:36 Didn't get such an error again for some time, but finally got it today - rollback fixed it! Thanks! And what if I do accidentally commit such a file?
Well, not nuclear launch codes, but something like a assembly signing keyfile? – Maxim Zaslavsky Jul 9 '10 at 7:57 Various discussion here: hgbook. Red-bean.Com/read/…, but you're basically screwed - You can dig around in the repo store and "fix" the problem, but you have a problem because you don't know if anyone pulled the change and thus has a local history with the change (and now you've created awful inconsistencies in version histories).
– Nick Bastin Jul 9 '10 at 16:33.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.