The hg strip option --no-backup uses the same short option (-n) as the --dry- run option of other Mercurial commands. In this particular case the --no-backup option on strip does the exact opposite of what a naive user (like me) would expect when one executes hg strip -n. This is particular bad, because I did rely on the superb user interface of Mercurial and never expected to loose all chances of recovering from a strip when all I wanted was to see what a strip would actually strip from my history.
The hg update, hg revert use -C for --clean/--no-backup. There are other commands with nonstandard --dry-run behaviour: The hg merge command has -P for --preview (no merge is performed)
Fixed by http://selenic.com/repo/hg/rev/900eee0778d1 Matt Mackall <mpm@selenic.com> strip: ignore -n (issue3326) (BC) (please test the fix)
--- Bug imported by bugzilla@serpentine.com 2012-05-12 09:29 EDT --- This bug was previously known as _bug_ 3326 at http://mercurial.selenic.com/bts/issue3326