From: John Brooks <john@fastquake.com>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andy Whitcroft <apw@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] checkpatch: Change format of --color argument to --color[=WHEN]
Date: Wed, 7 Jun 2017 13:41:31 +0000 [thread overview]
Message-ID: <20170607134131.GA19794@kitsune.fastquake.com> (raw)
In-Reply-To: <efe43bdbad400f39ba691ae663044462493b0773.1496799721.git.joe@perches.com>
On Tue, Jun 06, 2017 at 06:50:06PM -0700, Joe Perches wrote:
> From: John Brooks <john@fastquake.com>
>
> The boolean --color argument did not offer the ability to force colourized
> output even if stdout is not a terminal. Change the format of the argument
> to the familiar --color[=WHEN] construct as seen in common Linux utilities
> such as git, ls and dmesg, which allows the user to specify whether to
> colourize output "always", "never", or "auto" when the output is a terminal.
> The default is "auto".
>
> The old command-line uses of --color and --no-color are unchanged.
>
> Signed-off-by: John Brooks <john@fastquake.com>
> Signed-off-by: Joe Perches <joe@perches.com>
Thanks for doing the V3 for me :)
I was going to but had other work to do last night.
John
prev parent reply other threads:[~2017-06-07 13:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 22:27 [PATCH] checkpatch: Change format of --color argument to --color[=WHEN] John Brooks
2017-06-05 23:10 ` Joe Perches
2017-06-05 23:28 ` John Brooks
2017-06-06 5:48 ` Adam Borowski
2017-06-06 17:07 ` [PATCH v2] " John Brooks
2017-06-06 19:21 ` Joe Perches
2017-06-06 19:56 ` John Brooks
2017-06-06 20:03 ` Joe Perches
2017-06-07 1:50 ` [PATCH V3] " Joe Perches
2017-06-07 13:41 ` John Brooks [this message]
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=20170607134131.GA19794@kitsune.fastquake.com \
--to=john@fastquake.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@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