Notes"hg qimport -r BAD:tip<br />
<br />
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<br />
<br />
hg qpop -a<br />
<br />
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."Unfurl
NotesFinally 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."Unfurl
Notes"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."Unfurl
Notes"This page describes how to create such repositories accessible via a shared ssh account without needing to give full shell access to other people. "Unfurl
Notes"The Subversion project shouldn't spend any more time trying to make Subversion a better version control tool for non-huge open source projects."FeedEmbedUnfurl
Converting The Repos | .: SNH Homepage :.
iBanjo » Blog Archive » Subversion’s Future?