move changes to branch retroactively?

[Matthew Turk]

On Thu, Jan 8, 2015 at 9:51 AM, Neal Becker <ndbecker2 at gmail.com> wrote:

> Matthew Turk wrote:
>
> > Hi Neal,
> >
> > On Thu, Jan 8, 2015 at 9:35 AM, Neal Becker <ndbecker2 at gmail.com> wrote:
> >
> >> I have 2 commits to default that I'd now like to move off of default
> onto
> >> a new
> >> branch.  Can I do this?
> >>
> >
> > Yup, you can do this with rebase (or rebase --keep if you don't want to
> > delete the changes or if they are already in public phase).  Just rebase
> > onto your destination branch.
> >
> > -Matt
>
> Thanks!  So what are the exact steps needed?
>
> 1st rev I want to move is 1116.  There is also it's child 1117, which is
> currently tip.
>
> 1. Create new branch.
> 2. Commit new branch.
> 3. rebase ?
>

What I would do is basically that -- someone else might have a better
suggestion, though.  I would update to where I want the new branch.  Create
it.  Commit.  Then, "hg rebase -d . -s 1116" which rebases onto current
revision, starting at revision 1116 and all its descendants.

-Matt


>
> (I'm using the tortoisehg gui, so not sure of the hg commands)
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20150108/6a645e9e/attachment-0002.html>