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 0/2] format-patch: produce non colorized patches when color.ui=always
Date: Tue, 13 Sep 2011 01:46:39 +0800 [thread overview]
Message-ID: <1315849601-26497-1-git-send-email-pangyanhan@gmail.com> (raw)
Hi list,
This 2-patch series has been rerolled with Jeff's suggestions.
For patch 1/2, I've renamed the new test file to t4051-format-patch-config.sh
and changed the description to "check that format-patch does not respect
porcelain config". In addition, I've slightly reworded the commit message to
include the date of the commit (c9bfb953) which introduces the regression.
For patch 2/2, as per Jeff's recommendation, teach git_format_config to
intercept color.ui in the same way as commit f3aafa4 (Disable color detection
during format-patch, 2006-07-09). This is inline with the way we avoid passing
down diff.color and color.diff to git_log_config and config functions further
down the callchain.
Pang Yan Han (2):
format-patch: demonstrate that color.ui=always produces colorized
patches
format-patch: produce non colorized patches when ui.color=always
builtin/log.c | 3 ++-
t/t4051-format-patch-config.sh | 23 +++++++++++++++++++++++
2 files changed, 25 insertions(+), 1 deletions(-)
create mode 100755 t/t4051-format-patch-config.sh
--
1.7.7.rc0.190.gb47b6
next 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 Pang Yan Han [this message]
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 ` [PATCH/RFCv2 2/2] format-patch: produce non colorized patches when ui.color=always Pang Yan Han
2011-09-12 18:08 ` 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-1-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).