From: "George Spelvin" <linux@horizon.com>
To: git@vger.kernel.org
Cc: linux@horizon.com
Subject: Is there a way to cherry-pick a merge?
Date: 14 Jun 2013 15:37:29 -0400 [thread overview]
Message-ID: <20130614193729.17663.qmail@science.horizon.com> (raw)
Sometimes I'd like to repeat a previously performed merge, preserving
the commit message. And, if possible, the conflict resolutions.
"git cherry-pick -m 1 <commit>" gets me the changes, but makes an
ordinary single-parent commit, not a merge.
"git rebase -p --onto HEAD commit^ commit" does the right thing,
but has two annoying properties:
1) It actually checks out "commit", then goes back to HEAD, thus
forcing a lot of recompiltion of source files that experience
no net change from the operation.
2) Because it's intended for multi-step use, it stops and waits for
confirmation if there are rerere changes. I'd rather it just did the
commit if there are no remaining conflict markers, and I'll reset or
amend it if I'm not happy with the result.
Does something like this exist already?
Thank you!
next reply other threads:[~2013-06-14 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 19:37 George Spelvin [this message]
2013-06-14 19:44 ` Is there a way to cherry-pick a merge? Junio C Hamano
2013-06-14 21:36 ` George Spelvin
2013-06-14 21:54 ` Junio C Hamano
2013-06-15 3:03 ` George Spelvin
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=20130614193729.17663.qmail@science.horizon.com \
--to=linux@horizon.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 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).