EditingHistory - Mercurial
http://mercurial.selenic.com/wiki/EditingHistory
"hg qimport -r BAD:tip
will import the changesets into MQ. You can find newly created patches in .hg/patches. Those patches are nevertheless still applied, to strip them from the history, you need the qpop command. Issue
hg qpop -a
Now all changes since revision BAD are no longer available in your repository history. They are saved as patches in .hg/patches - and only there."
ConcatenatingChangesets - Mercurial
http://mercurial.selenic.com/wiki/ConcatenatingChangesets
"Concatenating multiple changesets into one"
Publishing Mercurial Clones - MDC
https://developer.mozilla.org/En/Publishing_Mercurial_Clones
Finally figured out how to setup my own repos at hg.mozilla.org "When working with Mercurial, it is often nice to publish your changes on a server so others can examine and work with them as well. If you have commit access to CVS, you should have an LDAP account, and that should allow you to push to hg.mozilla.org. If you do, you can create clones in the /users directory and share them with others."
Hg-Git Mercurial Plugin - GitHub
http://github.com/blog/439-hg-git-mercurial-plugin
Mercurial Queues - Mozilla Developer Center
http://developer.mozilla.org/en/Mercurial_Queues
"Mercurial Queues, or MQ, is a Mercurial extension that lets you keep work in progress as mutable patches, instead of as immutable changesets. ... The output of a developer (on a good day, anyway) is patches. The MQ extension lets you treat a stack of patches as works-in-progress. You can apply them as Mercurial changesets, unapply them, edit them, and when they're done, turn them into permanent changesets and push them."
Push to try Rooftop lab
http://blog.mozilla.com/jorendorff/2008/08/18/push-to-try
SharedSSH - Mercurial
http://www.selenic.com/mercurial/wiki/index.cgi/SharedSSH
"This page describes how to create such repositories accessible via a shared ssh account without needing to give full shell access to other people. "
Converting The Repos | .: SNH Homepage :.
http://ww2.samhart.com/node/50
"Finally, I tried hgsvn, and it worked like a charm."
iBanjo » Blog Archive » Subversion’s Future?
http://blog.red-bean.com/sussman?p=90
"The Subversion project shouldn't spend any more time trying to make Subversion a better version control tool for non-huge open source projects."