From: Leonid Podolny <leonidp.lists@gmail.com>
To: weigelt@metux.de
Cc: git@vger.kernel.org
Subject: Re: Rebasing multiple branches
Date: Wed, 22 Dec 2010 16:54:46 +0200 [thread overview]
Message-ID: <4D121136.6050906@gmail.com> (raw)
In-Reply-To: <20101222143654.GA4829@nibiru.local>
On 12/22/2010 04:36 PM, Enrico Weigelt wrote:
> 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
Ah, nice. I didn't notice the -p option. However, the man page advises
against using -p and -i together.
next prev parent reply other threads:[~2010-12-22 14:54 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
2010-12-22 14:54 ` Leonid Podolny [this message]
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=4D121136.6050906@gmail.com \
--to=leonidp.lists@gmail.com \
--cc=git@vger.kernel.org \
--cc=weigelt@metux.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).