From: "Nazri Ramliy" <ayiehere@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH (Eek!)] git diff does not honor --no-ext-diff
Date: Wed, 26 Nov 2008 15:12:25 +0800 [thread overview]
Message-ID: <544dda350811252312u7ef5533bwb20b37640d861487@mail.gmail.com> (raw)
Hello list,
git-diff does not honor the --no-ext-diff option in both cases when the external
diff program is set via diff.external and gitattributes.
Is this intentional? If not the following patch seems to fix it.
I think there must be a cleaner way of fixing this than doing it by
`hand' hence the Eek!
Nazri.
builtin-diff.c | 14 +++++++++++++-
1 files changed, 13 insertions(+), 1 deletions(-)
diff --git a/builtin-diff.c b/builtin-diff.c
index 7ceceeb..4ac7e15 100644
--- a/builtin-diff.c
+++ b/builtin-diff.c
@@ -290,6 +290,19 @@ int cmd_diff(int argc, const char **argv, const
char *prefix)
/* Otherwise, we are doing the usual "git" diff */
rev.diffopt.skip_stat_unmatch = !!diff_auto_refresh_index;
+ DIFF_OPT_SET(&rev.diffopt, ALLOW_EXTERNAL);
+ /*
+ * Do we have --no-ext-diff and have external diff setup via either
+ * gitconfig or gitattributes, then clear ALLOW_EXTERNAL by hand. Eek.
+ */
+ for (i = 1; i < argc; i++) {
+ const char *arg = argv[i];
+ if (!strcmp(arg, "--"))
+ break;
+ else if (!strcmp(arg, "--no-ext-diff"))
+ DIFF_OPT_CLR(&rev.diffopt, ALLOW_EXTERNAL);
+ }
+
if (nongit)
die("Not a git repository");
argc = setup_revisions(argc, argv, &rev, NULL);
@@ -298,7 +311,6 @@ int cmd_diff(int argc, const char **argv, const
char *prefix)
if (diff_setup_done(&rev.diffopt) < 0)
die("diff_setup_done failed");
}
- DIFF_OPT_SET(&rev.diffopt, ALLOW_EXTERNAL);
DIFF_OPT_SET(&rev.diffopt, RECURSIVE);
DIFF_OPT_SET(&rev.diffopt, ALLOW_TEXTCONV);
next reply other threads:[~2008-11-26 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 7:12 Nazri Ramliy [this message]
2008-11-26 7:52 ` [PATCH (Eek!)] git diff does not honor --no-ext-diff Junio C Hamano
2008-11-26 7:59 ` René Scharfe
2008-11-26 10:01 ` Nazri Ramliy
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=544dda350811252312u7ef5533bwb20b37640d861487@mail.gmail.com \
--to=ayiehere@gmail.com \
--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).