From: Pang Yan Han <pangyanhan@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net,
martin.von.zweigbergk@gmail.com, sdaoden@googlemail.com,
ib@wupperonline.de, Pang Yan Han <pangyanhan@gmail.com>
Subject: [PATCH/RFCv2 2/2] format-patch: produce non colorized patches when ui.color=always
Date: Tue, 13 Sep 2011 01:46:41 +0800 [thread overview]
Message-ID: <1315849601-26497-3-git-send-email-pangyanhan@gmail.com> (raw)
In-Reply-To: <1315849601-26497-1-git-send-email-pangyanhan@gmail.com>
commit c9bfb953 (want_color: automatically fallback to color.ui,
2011-08-17) introduced a regression where format-patch produces colorized
patches when color.ui is set to "always".
In f3aafa4 (Disable color detection during format-patch, 2006-07-09),
git_format_config was taught to intercept diff.color to avoid passing it
down to git_log_config and later, git_diff_ui_config.
Teach git_format_config to intercept color.ui in the same way.
Helped-by: Jeff King <peff@peff.net>
Signed-off-by: Pang Yan Han <pangyanhan@gmail.com>
---
builtin/log.c | 3 ++-
t/t4051-format-patch-config.sh | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/builtin/log.c b/builtin/log.c
index d760ee0..99f8c4c 100644
--- a/builtin/log.c
+++ b/builtin/log.c
@@ -608,7 +608,8 @@ static int git_format_config(const char *var, const char *value, void *cb)
string_list_append(&extra_cc, value);
return 0;
}
- if (!strcmp(var, "diff.color") || !strcmp(var, "color.diff")) {
+ if (!strcmp(var, "diff.color") || !strcmp(var, "color.diff") ||
+ !strcmp(var, "color.ui")) {
return 0;
}
if (!strcmp(var, "format.numbered")) {
diff --git a/t/t4051-format-patch-config.sh b/t/t4051-format-patch-config.sh
index cea9c7d..35b349e 100755
--- a/t/t4051-format-patch-config.sh
+++ b/t/t4051-format-patch-config.sh
@@ -13,7 +13,7 @@ test_expect_success setup '
git commit -m "commit2"
'
-test_expect_failure 'format patch with ui.color=always generates non colorized patch' '
+test_expect_success 'format patch with ui.color=always generates non colorized patch' '
git config color.ui always &&
git format-patch -1 &&
mv 0001-commit2.patch actual &&
--
1.7.7.rc0.190.gb47b6
next prev parent reply other threads:[~2011-09-12 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 17:46 [PATCH/RFCv2 0/2] format-patch: produce non colorized patches when color.ui=always Pang Yan Han
2011-09-12 17:46 ` [PATCH/RFCv2 1/2] format-patch: demonstrate that color.ui=always produces colorized patches Pang Yan Han
2011-09-12 18:07 ` Junio C Hamano
2011-09-12 17:46 ` Pang Yan Han [this message]
2011-09-12 18:08 ` [PATCH/RFCv2 2/2] format-patch: produce non colorized patches when ui.color=always Junio C Hamano
2011-09-12 18:43 ` Junio C Hamano
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=1315849601-26497-3-git-send-email-pangyanhan@gmail.com \
--to=pangyanhan@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ib@wupperonline.de \
--cc=martin.von.zweigbergk@gmail.com \
--cc=peff@peff.net \
--cc=sdaoden@googlemail.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).