git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Santi Béjar" <santi@agolina.net>
To: "David Brown" <git@davidb.org>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Help breaking up a large merge.
Date: Thu, 18 Sep 2008 17:55:34 +0200	[thread overview]
Message-ID: <adf1fd3d0809180855l42af4fb6l67275daef0d2a529@mail.gmail.com> (raw)
In-Reply-To: <20080918152154.GA27019@linode.davidb.org>

On Thu, Sep 18, 2008 at 5:21 PM, David Brown <git@davidb.org> wrote:
> Say we have a tree that we've been working on for a few months.  An
> outside vendor has also been working on the same tree during this
> time, and we need to merge with their work.
>
> The difficulty I'm having is that there are a lot of conflicts
> resulting from the merge (expected), and it would be nice to somehow
> be able to work on a smaller set of these conflicts at a time.

If the two (or at least one) branches have sufficient isolated commits
you can recreate the merges that could have happened, as is explained
(for monotone) in:

http://www.venge.net/mtn-wiki/ZipperMerge

Another option is to rebase one branch onto the other.

Even another option is to merge the two branches but use the rebased
tree to resolve the conflicts.

They are not for parallel merge resolution, but at least you can do
them incrementally.

HTH,
Santi

  reply	other threads:[~2008-09-18 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 15:21 Help breaking up a large merge David Brown
2008-09-18 15:55 ` Santi Béjar [this message]
2008-09-18 16:25   ` David Brown
2008-09-18 16:41 ` Johannes Sixt
2008-09-18 17:40 ` Avery Pennarun
2008-09-18 17:47   ` David Brown

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=adf1fd3d0809180855l42af4fb6l67275daef0d2a529@mail.gmail.com \
    --to=santi@agolina.net \
    --cc=git@davidb.org \
    --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).