From: David Aguilar <davvid@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
John Keeping <john@keeping.me.uk>,
Charles Bailey <charles@hashpling.org>,
Theodore Ts'o <tytso@mit.edu>
Subject: [RFC PATCH 2/3] mergetools/kdiff3: allow opting-out of auto-merges
Date: Thu, 9 May 2013 02:13:29 -0700 [thread overview]
Message-ID: <1368090810-40596-2-git-send-email-davvid@gmail.com> (raw)
In-Reply-To: <1368090810-40596-1-git-send-email-davvid@gmail.com>
By default, "git mergetool" passes the `--auto` flag to `kdiff3` when
merging a file. The `--auto` flag tells `kdiff3` to skip showing the
GUI and automatically save the merged result when it is able to
trivially resolve a merge.
Some users prefer to eyeball the merged result using mergetool and the
use of `--auto` prevents them from doing so. Add a configuration
variable to allow opting-out of the auto-merge feature.
Signed-off-by: David Aguilar <davvid@gmail.com>
---
Marked "RFC" because I am kinda against adding more configuration
variables. Someone ran into this and I did personally find the
behavior a bit surprising. Alternatively, we *could* change the
default behavior, but I am not convinced that doing so is a good idea
either, hence this patch. Other then the "kinda against",
it does make the behavior less surprising.
Documentation/merge-config.txt | 9 +++++++++
mergetools/kdiff3 | 20 ++++++++++++++++++--
2 files changed, 27 insertions(+), 2 deletions(-)
diff --git a/Documentation/merge-config.txt b/Documentation/merge-config.txt
index d78d6d8..3bd5f21 100644
--- a/Documentation/merge-config.txt
+++ b/Documentation/merge-config.txt
@@ -59,6 +59,15 @@ merge.tool::
include::mergetools-merge.txt[]
+mergetool.kdiff3.manualMerge::
+ Tell Git that not to use `kdiff3`'s auto-merge feature.
+ By default, "git mergetool" passes the `--auto` flag to `kdiff3`
+ when merging a file. The `--auto` flag tells `kdiff3` to skip
+ showing the GUI and automatically save the merged result when it
+ is able to trivially resolve a merge. The `--auto` flag will
+ not be used when this variable is set to `true`. False by
+ default.
+
merge.verbosity::
Controls the amount of output shown by the recursive merge
strategy. Level 0 outputs nothing except a final error
diff --git a/mergetools/kdiff3 b/mergetools/kdiff3
index a30034f..d0acda9 100644
--- a/mergetools/kdiff3
+++ b/mergetools/kdiff3
@@ -1,3 +1,18 @@
+kdiff3_initialized=
+kdiff3_args=--auto
+
+kdiff3_init () {
+ if test -n "$kdiff3_initialized"
+ then
+ return
+ fi
+ if test "$(git config --bool mergetool.kdiff3.manualMerge)" = true
+ then
+ kdiff3_args=
+ fi
+ kdiff3_initialized=true
+}
+
diff_cmd () {
"$merge_tool_path" \
--L1 "$MERGED (A)" --L2 "$MERGED (B)" \
@@ -5,16 +20,17 @@ diff_cmd () {
}
merge_cmd () {
+ kdiff3_init
if $base_present
then
- "$merge_tool_path" --auto \
+ "$merge_tool_path" $kdiff3_args \
--L1 "$MERGED (Base)" \
--L2 "$MERGED (Local)" \
--L3 "$MERGED (Remote)" \
-o "$MERGED" "$BASE" "$LOCAL" "$REMOTE" \
>/dev/null 2>&1
else
- "$merge_tool_path" --auto \
+ "$merge_tool_path" $kdiff3_args \
--L1 "$MERGED (Local)" \
--L2 "$MERGED (Remote)" \
-o "$MERGED" "$LOCAL" "$REMOTE" \
--
1.8.3.rc1.38.g0f1704c
next prev parent reply other threads:[~2013-05-09 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 9:13 [PATCH 1/3] mergetools/kdiff3: do not use --auto when diffing David Aguilar
2013-05-09 9:13 ` David Aguilar [this message]
2013-05-09 9:13 ` [RFC PATCH 3/3] Makefile: avoid deprecation warnings on OS X 10.8 David Aguilar
2013-05-09 15:14 ` John Keeping
2013-05-09 23:21 ` David Aguilar
2013-05-09 16:10 ` [RFC PATCH 2/3] mergetools/kdiff3: allow opting-out of auto-merges Junio C Hamano
2013-05-09 17:23 ` John Keeping
2013-05-09 19:15 ` Junio C Hamano
2013-05-09 22:17 ` David Aguilar
2013-05-10 5:41 ` Charles Bailey
2013-05-10 18:40 ` David Aguilar
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=1368090810-40596-2-git-send-email-davvid@gmail.com \
--to=davvid@gmail.com \
--cc=charles@hashpling.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=john@keeping.me.uk \
--cc=tytso@mit.edu \
/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).