From: "SZEDER Gábor" <szeder@ira.uka.de>
To: "Peter Valdemar Mørch (Lists)" <4ux6as402@sneakemail.com>
Cc: git@vger.kernel.org
Subject: Re: git merge after git cherry-pick?
Date: Wed, 23 Jul 2008 19:56:00 +0200 [thread overview]
Message-ID: <20080723175600.GL22606@neumann> (raw)
In-Reply-To: <48876709.3090504@sneakemail.com>
On Wed, Jul 23, 2008 at 07:14:49PM +0200, "Peter Valdemar Mørch (Lists)" wrote:
> On a branch, b, made off of master, I've made the commits b1, b2, b3 and
> b4.
>
> Back on master, I need commit b1 and b3 immediately. So I:
>
> $ git checkout master
> $ git cherry-pick "b1's SHA"
> $ git cherry-pick "b3's SHA"
>
> Now, both b and master contain b1 and b3. How do I now create a log of
> "what remains to be merged from b to master", i.e. only b2 and b4? And
> how do I merge b2 and b4 to master, so master's log shows b1, b3, b2 and
> b4 and doesn't show b1 and b3 twice, which is what I get if I:
>
> $ git merge b
>
> after the cherry-picks above. Also I noticed, that if I merge master
> into b (to keep up-to-date with master) b1 and b3 are also mentioned
> twice.
You could use 'git rebase' for that.
e.g. now the history of your master and b branches look like this:
o---X---b1'---b3'---Y master
\
b1---b2---b3---b4 b
The command 'git rebase master b' will then turn this history into the
following:
o---X---b1'---b3'---Y master
\
b2---b4 b
After this 'git merge b' will do what you would like it to do.
Regards,
Gábor
next prev parent reply other threads:[~2008-07-23 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 17:14 git merge after git cherry-pick? "Peter Valdemar Mørch (Lists)"
2008-07-23 17:56 ` SZEDER Gábor [this message]
2008-07-23 19:35 ` "Peter Valdemar Mørch (Lists)"
2008-07-23 17:56 ` Jakub Narebski
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=20080723175600.GL22606@neumann \
--to=szeder@ira.uka.de \
--cc=4ux6as402@sneakemail.com \
--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.