> Because rebasing was literally an afterthought - a plugin Hg extensions are just as much part of hg as the core functionality. It's just that they're opt-in

> Because rebasing was literally an afterthought - a plugin Hg extensions are just as much part of hg as the core functionality. It's just that they're opt-in parts many users don't need and thus don't have to see. If your workflow requires history editing, then fine, enable rebase and histedit. As for mq, I think I've only used it in a script where I converted an ancient CVS repo and rewrote entire parts of the history to remove stuff that should never have been in there to begin with. It's powerful, but rarely required by anyone, and thus is opt-in as well.