From: Howard Miller <howard@e-learndesign.co.uk>
To: Tim Guirgies <lt.infiltrator@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Can't get git rebase --onto to work
Date: Thu, 2 Jun 2011 12:28:47 +0100 [thread overview]
Message-ID: <BANLkTimJQPvJ2oJh9BbcoZ-1ktSdAzTm2g@mail.gmail.com> (raw)
In-Reply-To: <20110602111825.GC4709@Imperial-SSD-Overlord>
> Can you please also point out which section of the doc caused you
> confusion?
>
>
Ok... this is exactly my situation (and solution)
"First let’s assume your topic is based on branch next. For example, a
feature developed in topic depends on some functionality which is
found in next.
o---o---o---o---o master
\
o---o---o---o---o next
\
o---o---o topic
We want to make topic forked from branch master; for example, because
the functionality on which topic depends was merged into the more
stable master branch. We want our tree to look like this:
o---o---o---o---o master
| \
| o'--o'--o' topic
\
o---o---o---o---o next
We can get this using the following command:
git rebase --onto master next topic"
However, I didn't look at the HEADs (seems stupid now). What I was
aiming for was (simply) for 'master' to have the 'topic' branch
changes (the delta between next and topic being applied to master if
you will). The only outstanding step was to checkout master and merge
topic (which will always bee fast-forward, of course).
It's the topic branch that gets rebased - obvious (now) but I
interpreted it as the master branch getting modified (--onto master
i.e. play the changes 'onto' master and modify master).
I didn't read it carefully enough - makes sense now.
prev parent reply other threads:[~2011-06-02 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 10:17 Can't get git rebase --onto to work Howard Miller
2011-06-02 10:32 ` Carlos Martín Nieto
2011-06-02 10:38 ` Howard Miller
2011-06-02 10:38 ` Tim Guirgies
2011-06-02 10:43 ` Howard Miller
2011-06-02 10:52 ` Tim Guirgies
2011-06-02 10:58 ` Howard Miller
2011-06-02 11:18 ` David
2011-06-02 11:18 ` Tim Guirgies
2011-06-02 11:28 ` Howard Miller [this message]
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=BANLkTimJQPvJ2oJh9BbcoZ-1ktSdAzTm2g@mail.gmail.com \
--to=howard@e-learndesign.co.uk \
--cc=git@vger.kernel.org \
--cc=lt.infiltrator@gmail.com \
/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).