From: Enrico Weigelt <weigelt@metux.de>
To: git@vger.kernel.org
Subject: Re: Rebasing multiple branches
Date: Wed, 22 Dec 2010 15:36:55 +0100 [thread overview]
Message-ID: <20101222143654.GA4829@nibiru.local> (raw)
In-Reply-To: <4D10B44D.5090309@viscovery.net>
* Johannes Sixt <j.sixt@viscovery.net> wrote:
> Am 12/21/2010 14:40, schrieb Leonid Podolny:
> > B--o--o--o--o--o--o <--branch A
> > / \
> > o--o--A--o--E <--master C--o--o--o--D <--branch C
> > \ /
> > C--o--o--o--o--o--o <--branch B
> >
> > I would like to rebase all three branches A, B and C onto commit E,...
>
> git rebase master A
> git rebase master B
> git merge A
> git rebase -i HEAD C
>
> The last rebase I propose as interactive so that you can remove those
> commits before D~3 that you have already rebased, because they are likely
> to conflict unnecessarily, and you would --skip them anyway.
Why not this way ?
git checkout D
git rebase -p -i D~3 --onto C'
(C' is the merged branch of A' and B').
So:
git checkout branch_A -b rebasing_A
git rebase master # rebase old A to master
git checkout branch_B -b rebasing_B
git rebase master # rebase old B to master
git checkout -b rebased_merge
git merge rebasing_A # we're on B', merge in A'
git checkout branch_C
git rebase -p -i C --onto rebased_merge # set D~3..D ontop of it
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
next prev parent reply other threads:[~2010-12-22 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 13:40 Rebasing multiple branches Leonid Podolny
2010-12-21 14:06 ` Johannes Sixt
2010-12-22 14:36 ` Enrico Weigelt [this message]
2010-12-22 14:54 ` Leonid Podolny
2010-12-30 5:35 ` Enrico Weigelt
2010-12-31 14:55 ` Thomas Rast
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101222143654.GA4829@nibiru.local \
--to=weigelt@metux.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.