From: Stephen Hemminger <stephen@networkplumber.org>
To: Mathias Nyman <m.nyman@iki.fi>
Cc: netdev@vger.kernel.org, daniel@iogearbox.net,
alexei.starovoitov@gmail.com, aleksi.aalto@iki.fi
Subject: Re: [PATCH v2 net-next] ip: Add color output option
Date: Mon, 20 Apr 2015 10:16:02 -0700 [thread overview]
Message-ID: <20150420101602.361354d7@urahara> (raw)
In-Reply-To: <20150418103945.GA26334@iki.fi>
On Sat, 18 Apr 2015 13:39:45 +0300
Mathias Nyman <m.nyman@iki.fi> wrote:
> It is hard to quickly find what you are looking for in the output of
> the ip
> command. Color helps.
>
> This patch adds a '-c' flag to highlight these with individual colors:
> - interface name
> - ip address
> - mac address
> - up/down state
>
> Signed-off-by: Mathias Nyman <m.nyman@iki.fi>
I like the idea of this, it would be generally good across the board.
But the patch does not apply cleanly to the current version of iproute2.
And there are minor style issues. iproute2 in general ties to follow kernel style.
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#36:
new file mode 100644
ERROR: open brace '{' following enum go on the same line
#45: FILE: include/color.h:5:
+enum color_attr
+{
ERROR: open brace '{' following enum go on the same line
#195: FILE: lib/color.c:7:
+enum color
+{
ERROR: that open brace { should be on the previous line
#207: FILE: lib/color.c:19:
+static const char * const color_codes[] =
+{
ERROR: that open brace { should be on the previous line
#220: FILE: lib/color.c:32:
+static enum color attr_colors[] =
+{
ERROR: do not initialise statics to 0 or NULL
#229: FILE: lib/color.c:41:
+static int color_is_enabled = 0;
WARNING: Missing a blank line after declarations
#240: FILE: lib/color.c:52:
+ va_list args;
+ va_start(args, fmt);
next prev parent reply other threads:[~2015-04-20 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-18 10:39 [PATCH v2 net-next] ip: Add color output option Mathias Nyman
2015-04-20 17:16 ` Stephen Hemminger [this message]
2015-04-20 20:30 ` Mathias Nyman
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=20150420101602.361354d7@urahara \
--to=stephen@networkplumber.org \
--cc=aleksi.aalto@iki.fi \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=m.nyman@iki.fi \
--cc=netdev@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