Christian Brabandt wrote:
> On Mi, 02 Apr 2014, Danek Duvall wrote:
>
> > I'm in the same boat. I've been using MQ for years and am comfortable with
> > it, and haven't had the time to try out obsolescence in any serious way,
> > though I'm actually quite excited about it, since I'd love to have the
> > history of my patch changes for the duration of the patch. I tried out
> > pbranch several years ago, but it was just too wild, and the merges were
> > horrendous.
>
> Can someone explain in little more detail how to use the new recommended
> way to deal with patches if mq becomes un-supported?
You can start here:
http://mercurial.selenic.com/wiki/ChangesetEvolution
and the materials linked from there. There's also
http://hg-lab.logilab.org/doc/mutable-history/html/
which includes a MQ-refugee page.
Though the interfaces MQ provides won't be removed for a long time, if
ever; the mercurial guys are very strict about backwards compatibility.
Danek
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
