From: Sylvain Rabot <srabot@steek.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, sylvain@abstraction.fr,
Sylvain Rabot <srabot@steek.com>
Subject: [PATCH] documentation: git-mergetool updated to warn against builtin tools invocations
Date: Wed, 2 Jun 2010 19:57:33 +0200 [thread overview]
Message-ID: <1275501453-13081-1-git-send-email-srabot@steek.com> (raw)
For known tools such as meld, diffuse, p4merge, git-mergetool ignores the
mergetool.<tool>.* configurations. It took me a while to understand why my
mergetool.diffuse.cmd configuration was not taken care of.
This documentation update warns against this behavior and explains how
to setup a customized command line invocation for known diff tools.
Signed-off-by: Sylvain Rabot <srabot@steek.com>
---
Documentation/git-mergetool.txt | 15 +++++++++++++++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-mergetool.txt b/Documentation/git-mergetool.txt
index 55735fa..ac41d7c 100644
--- a/Documentation/git-mergetool.txt
+++ b/Documentation/git-mergetool.txt
@@ -45,6 +45,21 @@ Instead of running one of the known merge tool programs,
by specifying the command line to invoke in a configuration
variable `mergetool.<tool>.cmd`.
+
+Be aware that 'git mergetool' has some predefined invocation commands builtin
+for known diff tools like meld, diffuse, p4merge ... etc. It means that if
+you set the merge.tool configuration to one of these tools, the
+mergetool.<tool>.* configurations will not be taken care of. If you
+really want to customize the invocation of one of these tools,
+set `merge.tool` to "custom" or whatever you want and `mergetool.custom.cmd`
+to "/usr/bin/<tool> $LOCAL $MERGED $REMOTE"
++
+-------------
+[merge]
+ tool = diffuse-custom
+[mergetool "diffuse-custom"]
+ cmd = diffuse $LOCAL $MERGED $REMOTE
+-------------
++
When 'git mergetool' is invoked with this tool (either through the
`-t` or `--tool` option or the `merge.tool` configuration
variable) the configured command line will be invoked with `$BASE`
--
1.7.1
next reply other threads:[~2010-06-02 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 17:57 Sylvain Rabot [this message]
2010-06-02 23:38 ` [PATCH] documentation: git-mergetool updated to warn against builtin tools invocations Junio C Hamano
2010-06-03 7:45 ` Michael J Gruber
2010-06-03 10:55 ` Sylvain Rabot
2010-06-04 21:29 ` Sylvain Rabot
2010-06-07 12:50 ` Ramkumar Ramachandra
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=1275501453-13081-1-git-send-email-srabot@steek.com \
--to=srabot@steek.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sylvain@abstraction.fr \
/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).