From: David Ahern <dsahern@gmail.com>
To: Phil Sutter <phil@nwl.cc>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, Till Maas <opensource@till.name>
Subject: Re: [iproute PATCH v5 1/2] Make colored output configurable
Date: Fri, 17 Aug 2018 14:22:50 -0600 [thread overview]
Message-ID: <070af332-d19e-325c-3c13-a8575e914f40@gmail.com> (raw)
In-Reply-To: <20180817163846.27578-1-phil@nwl.cc>
On 8/17/18 10:38 AM, Phil Sutter wrote:
> Allow for -color={never,auto,always} to have colored output disabled,
> enabled only if stdout is a terminal or enabled regardless of stdout
> state.
>
> Signed-off-by: Phil Sutter <phil@nwl.cc>
> ---
> Changes since v1:
> - Allow to override isatty() check by specifying '-color' flag more than
> once.
> - Document new behaviour in man pages.
>
> Changes since v2:
> - Implement new -color=foo syntax.
> - Update commit message and man page texts accordingly.
>
> Changes since v3:
> - Fix typo in tc/tc.c causing compile error.
>
> Changes since v4:
> - Make matches_color() return boolean.
> ---
> bridge/bridge.c | 3 +--
> include/color.h | 9 +++++++++
> ip/ip.c | 3 +--
> lib/color.c | 33 ++++++++++++++++++++++++++++++++-
> man/man8/bridge.8 | 13 +++++++++++--
> man/man8/ip.8 | 13 +++++++++++--
> man/man8/tc.8 | 13 +++++++++++--
> tc/tc.c | 3 +--
> 8 files changed, 77 insertions(+), 13 deletions(-)
>
LGTM.
Reviewed-by: David Ahern <dsahern@gmail.com>
prev parent reply other threads:[~2018-08-17 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 9:37 [iproute PATCH v4] Make colored output configurable Phil Sutter
2018-08-16 13:06 ` David Ahern
2018-08-16 15:00 ` Phil Sutter
2018-08-17 16:24 ` Stephen Hemminger
2018-08-17 16:38 ` [iproute PATCH v5 1/2] " Phil Sutter
2018-08-17 16:38 ` [iproute PATCH 2/2] lib: Make check_enable_color() return boolean Phil Sutter
2018-08-17 20:22 ` David Ahern [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=070af332-d19e-325c-3c13-a8575e914f40@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=opensource@till.name \
--cc=phil@nwl.cc \
--cc=stephen@networkplumber.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).