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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
