From: "\"Peter Valdemar Mørch (Lists)\"" <4ux6as402@sneakemail.com>
To: git@vger.kernel.org
Subject: git merge after git cherry-pick?
Date: Wed, 23 Jul 2008 19:14:49 +0200 [thread overview]
Message-ID: <48876709.3090504@sneakemail.com> (raw)
Hi,
Still being a newbie...
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.
I did notice that cherry-pick created new SHA1 IDs for the commits for
b1 and b3 on master (as indeed man cherry-pick also says). Maybe
cherry-pick is not the right tool for the job. Is there another way to
"copy"/"merge" only b1 and b3 (but not b2 and b4) from b into master
maintaining merge history and avoiding them being mentioned twice later?
At the time of writing b1-b4, I did not know that b1 and b3 would be
needed separately, so I didn't put (b1 and b3) and (b2 and b4) on
separate branches. I did notice though, that they weren't an intricate
part of "the new feature". Is it required that I then do the work in
separate branches?
I hope this is possible as I'm thrilled with git!
Peter
--
Peter Valdemar Mørch
http://www.morch.com
next reply other threads:[~2008-07-23 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 17:14 "Peter Valdemar Mørch (Lists)" [this message]
2008-07-23 17:56 ` git merge after git cherry-pick? SZEDER Gábor
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=48876709.3090504@sneakemail.com \
--to=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.