From: Andreas Ericsson <ae@op5.se>
To: "Dirk Süsserott" <newsletter@dirk.my1.cc>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Rebase a whole tree from one commit to another?
Date: Sat, 16 May 2009 09:35:33 +0200 [thread overview]
Message-ID: <4A0E6CC5.5090503@op5.se> (raw)
In-Reply-To: <4A0DC4CD.1030401@dirk.my1.cc>
Dirk Süsserott wrote:
> Hi alltogether.
>
> Let's say I have the following history:
>
> | | | | branch-c
> | | | |
> | | |/ branch-b
> | | |
> | |/ branch-a
> | |
> |/
> | master
>
> Now I checkout master, do some changes, and commit them to the master
> branch. Let's call that new-master:
>
> | new-master
> | | | | | branch-c
> | | | | |
> | | | |/ branch-b
> | | | |
> | | |/ branch-a
> | | |
> | |/
> \| master
>
> I want to rebase my branches a, b, c to the new master. The clumsy way
> would be:
>
> git rebase new-master branch-a
> git rebase branch-a branch-b
> git rebase branch-b branch-c
>
> The question is: Is there a way to rebase the whole tree (master ->
> branch-a -> branch-b -> branch-c) from master to new-master with a
> single command?
>
No. You could merge all the branches that forked from master, rebase
the merged branch to new-master and then undo the merge-commit though,
but that would still mean three commands (and most likely some
conflict resolution). Assuming you have (a lot) more than three
branches, this might be a way forward for you.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Register now for Nordic Meet on Nagios, June 3-4 in Stockholm
http://nordicmeetonnagios.op5.org/
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
next prev parent reply other threads:[~2009-05-16 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 19:38 Rebase a whole tree from one commit to another? Dirk Süsserott
2009-05-16 7:35 ` Andreas Ericsson [this message]
2009-05-16 13:49 ` Clemens Buchacher
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=4A0E6CC5.5090503@op5.se \
--to=ae@op5.se \
--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 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.