From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "William Tanksley" <wtanksleyjr+git@gmail.com>, git@vger.kernel.org
Subject: Re: Can git be stopped from inserting conflict markers during a merge?
Date: Sun, 9 Mar 2008 11:24:21 +1300 [thread overview]
Message-ID: <46a038f90803081424s1a0091c6r4d9e24c62ef2bdd1@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0803081242040.5896@woody.linux-foundation.org>
On Sun, Mar 9, 2008 at 9:51 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> Do you want to just have both (with the base version, all three?) versions
> of the file in your directory?
If that's what he is after, git-mergetool will do it - normally as a
preparation to call xxdiff or something similar. William, perhaps
git-mergetool is what you are after? You can look at the source --
it's shell -- if you want to tweak it.
But I think that what mercurial does is similar to Arch and Bazaar
behaviour: it will update the file following "one side" of the merge,
and then generate a .rej file with the unapplied hunks coming from the
'other side'. This selection is arbitrary, and doesn't work on
octopus merges, so I end up not quite liking it. OTOH, if you open the
.rej file with emacs in diff mode, it's bloody useful for fixing up
patches so that they apply.
cheers,
m
next prev parent reply other threads:[~2008-03-08 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 17:55 Can git be stopped from inserting conflict markers during a merge? William Tanksley
2008-03-08 20:51 ` Linus Torvalds
2008-03-08 22:24 ` Martin Langhoff [this message]
2008-03-08 21:03 ` Jakub Narebski
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=46a038f90803081424s1a0091c6r4d9e24c62ef2bdd1@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wtanksleyjr+git@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).