From: Jeff King <peff@peff.net>
To: Uri Okrent <uokrent@gmail.com>
Cc: Jay Soffian <jaysoffian@gmail.com>,
The Git Mailing List <git@vger.kernel.org>
Subject: Re: Question: start mergetool with trivial differences already handled?
Date: Mon, 17 May 2010 18:41:17 -0400 [thread overview]
Message-ID: <20100517224117.GA12092@coredump.intra.peff.net> (raw)
In-Reply-To: <AANLkTilLX8fWto-xL261Bkj_2fhRDqBPakP7l83QNDBj@mail.gmail.com>
On Mon, May 17, 2010 at 03:23:11PM -0700, Uri Okrent wrote:
> I haven't found this to be the case. Is there a merge tool that can
> do this? I had assumed that git used some magic using the project's
> history in order to resolve conflicts in a smart way. Will a merge tool
> that only has $THEIRS, $OURS, and $BASE have enough information to
> resolve conflicts as smart as git itself does when it produces the
> unmerged file in your working tree?
Git uses only $THEIRS, $OURS, and $BASE to do the merge. It doesn't look
at the interim history at all.
> > Most of the tools that mergetool supports out-of-the-box perform 3-way
> > diffs, so I guess I'm curious what merge tool you're using.
> I use xxdiff or diffuse (or more frequently, vim ;))
If you're using xxdiff, try "Global > Merge" from the menu (or the
Ctrl-Alt-M shortcut) to have it automatically merge any non-contentious
bits.
-Peff
prev parent reply other threads:[~2010-05-17 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 20:47 Question: start mergetool with trivial differences already handled? Uri Okrent
2010-05-17 22:07 ` Jay Soffian
2010-05-17 22:23 ` Uri Okrent
2010-05-17 22:41 ` Jeff King [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=20100517224117.GA12092@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=uokrent@gmail.com \
/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).