From: Jonathan Nieder <jrnieder@gmail.com>
To: "Dirk Süsserott" <newsletter@dirk.my1.cc>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Q: rebasing (moving) a whole tree (not just one branch)
Date: Fri, 18 Mar 2011 15:26:37 -0500 [thread overview]
Message-ID: <20110318202637.GA23255@elie> (raw)
In-Reply-To: <4D83BB0A.8070307@dirk.my1.cc>
Hi Dirk,
Dirk Süsserott wrote:
> I'd like to rebase a whole tree from A to B. Not just a single
> branch, but a whole tree. Let's say I have the following history:
>
> --- A --- B
> |
> + -- C -- D
> |
> + E -- F
>
> I'd like to rebase C and its descendants from A to B
I'd suggest cheating by making a merge of D and F and "rebase -p"-ing
that. :)
To say something more sensible would probably require more information
about the particular application, though.
Hope that helps,
Jonathan
next prev parent reply other threads:[~2011-03-18 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 20:05 Q: rebasing (moving) a whole tree (not just one branch) Dirk Süsserott
2011-03-18 20:26 ` Jonathan Nieder [this message]
2011-03-18 21:14 ` Junio C Hamano
2011-03-18 21:34 ` Jonathan Nieder
2011-03-18 22:53 ` Johannes Sixt
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=20110318202637.GA23255@elie \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=newsletter@dirk.my1.cc \
/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).