From: Gregory Jefferis <jefferis@gmail.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Choosing a mergetool according to file type
Date: Fri, 26 Jun 2009 14:27:55 +0100 [thread overview]
Message-ID: <C66A8B6B.20617%jefferis@gmail.com> (raw)
In-Reply-To: <vpqd48rw68k.fsf@bauges.imag.fr>
Hi Matthieu,
Thanks for your reply.
On 2009-06-26 13:04, "Matthieu Moy" <Matthieu.Moy@imag.fr> wrote:
> Never used it, but man gitattributes says
>
> Performing a three-way merge
> merge
> [...]
> String
> 3-way merge is performed using the specified custom merge
> driver. The built-in 3-way merge driver can be explicitly specified by asking
> for "text" driver; the built-in "take the current branch"
> driver can be requested with "binary".
> [...]
> Defining a custom merge driver
>
> Is it not what you're looking for?
This defines the merge driver but not the mergetool. A mergetool is
presumably an interactive tool that helps you clean up failed automatic
merges. For my binary files the internal merge driver "binary" will be used
which as your quote points our keeps the local file and signals a conflict
if it is different from the remote file. I cannot define a custom merge
driver for my binary word files because I don't have such a program (which
would have to carry out the merge in a non-interactive fashion). As
mergetool I use a script that calls Word and that of course has to be
interactive.
Best,
Greg.
next prev parent reply other threads:[~2009-06-26 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A44A66B.10906@viscovery.net>
2009-06-26 11:04 ` Choosing a mergetool according to file type Gregory Jefferis
2009-06-26 11:29 ` Johannes Sixt
2009-06-26 12:04 ` Matthieu Moy
2009-06-26 13:27 ` Gregory Jefferis [this message]
2009-06-26 13:51 ` Matthieu Moy
2009-06-26 16:57 ` Junio C Hamano
2009-06-26 17:43 ` Gregory Jefferis
2009-06-26 17:03 ` Gregory Jefferis
2009-06-26 10:28 Gregory Jefferis
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=C66A8B6B.20617%jefferis@gmail.com \
--to=jefferis@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--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).