From: "Peter Harris" <git@peter.is-a-geek.org>
To: "Peter Valdemar Mørch (Lists)" <4ux6as402@sneakemail.com>
Cc: git@vger.kernel.org
Subject: Re: Git (svn) merge - but ignore certain commits?
Date: Thu, 8 Jan 2009 15:00:53 -0500 [thread overview]
Message-ID: <eaa105840901081200i2738dael10e2db35b7cb4750@mail.gmail.com> (raw)
In-Reply-To: <4966513C.1010707@sneakemail.com>
On Thu, Jan 8, 2009 at 2:17 PM, "Peter Valdemar Mørch (Lists)" wrote:
>
> E.g.:
>
> ---A---B---C---D--+ "master"
> \--E---F---G-/ "branch"
>
> Here I want F and G merged back to "master", but *not* E (which is a
> quick-and-dirty but safe version of B).
Stop and think about that for a second.
Rephrased, "I want to cherry pick a few commits to master using the
merge command".
That sounds rather silly when I put it that way. What do you really want? Hmm.
Maybe you want to cherry pick those commits. Maybe (if this is still
an unpublished branch), you want to "git rebase --onto B E" your
branch to get the non-dirty version of E, then merge.
Or maybe you do want to merge, but you're getting confused by not
seeing the automatic conflict markers. You could merge --no-commit the
branch, fix the conflicts (E conflicts logically with B, even if 'git
merge' doesn't automatically mark it as such -- 'git revert -n E' may
even do most of the work), and only then commit the merge revision.
Repeated merges from this state will not keep trying to import E
(since E is already in the history).
Peter Harris
prev parent reply other threads:[~2009-01-08 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-27 13:02 Git (svn) merge - but ignore certain commits? "Peter Valdemar Mørch (Lists)"
2008-12-28 0:17 ` Peter Harris
2009-01-08 17:49 ` "Peter Valdemar Mørch (Lists)"
2009-01-08 18:29 ` Peter Harris
2009-01-08 19:17 ` "Peter Valdemar Mørch (Lists)"
2009-01-08 20:00 ` Peter Harris [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=eaa105840901081200i2738dael10e2db35b7cb4750@mail.gmail.com \
--to=git@peter.is-a-geek.org \
--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 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).