From: David Ahern <dsahern@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>, netdev@vger.kernel.org
Cc: Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH v2 iproute2-next 0/5] bridge: json and color support
Date: Wed, 21 Feb 2018 09:48:53 -0700 [thread overview]
Message-ID: <b8c10b01-e8b2-fdd8-8ec4-97e39d962fa7@gmail.com> (raw)
In-Reply-To: <20180220192408.19763-1-stephen@networkplumber.org>
On 2/20/18 12:24 PM, Stephen Hemminger wrote:
> From: Stephen Hemminger <sthemmin@microsoft.com>
>
> This set of patches adds color and full JSON support to bridge command.
>
> The output format for bridge link command changes so that
> $ bridge link show
> and
> $ ip link show
> use same basic format.
>
> The "-c" flag to bridge changes from shortened form of "-compressvlan"
> to shortened form of "-color". Once again this is so that ip
> and bridge command take similar options.
>
> Lastly the JSON output format changes slightly but this
> could not impact any real user, because in several cases
> the current format was invalid JSON!
>
> v2
> rebase to updated iproute2-next
> use common pretty flag
> use common print_name_and_link
>
> Stephen Hemminger (5):
> bridge: implement json pretty print flag
> bridge: colorize output and use JSON print library
> bridge: add json support for link command
> bridge: update man page for new color and json changes
> ip: always print interface name in color
>
> bridge/br_common.h | 4 +-
> bridge/bridge.c | 16 ++-
> bridge/fdb.c | 279 ++++++++++++++++-------------------------
> bridge/link.c | 245 +++++++++++++++++++-----------------
> bridge/mdb.c | 354 ++++++++++++++++++++++-------------------------------
> bridge/vlan.c | 279 ++++++++++++++++-------------------------
> include/utils.h | 2 +-
> ip/ipaddress.c | 4 +-
> lib/utils.c | 4 +-
> man/man8/bridge.8 | 15 ++-
> 10 files changed, 521 insertions(+), 681 deletions(-)
>
series applied to iproute2-next.
prev parent reply other threads:[~2018-02-21 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 19:24 [PATCH v2 iproute2-next 0/5] bridge: json and color support Stephen Hemminger
2018-02-20 19:24 ` [PATCH v2 iproute2-next 1/5] bridge: implement json pretty print flag Stephen Hemminger
2018-02-20 19:24 ` [PATCH v2 iproute2-next 2/5] bridge: colorize output and use JSON print library Stephen Hemminger
2018-07-15 1:41 ` Roopa Prabhu
2018-08-29 1:17 ` Roopa Prabhu
2018-08-29 15:04 ` Stephen Hemminger
2018-02-20 19:24 ` [PATCH v2 iproute2-next 3/5] bridge: add json support for link command Stephen Hemminger
2018-02-20 19:24 ` [PATCH v2 iproute2-next 4/5] bridge: update man page for new color and json changes Stephen Hemminger
2018-02-20 19:24 ` [PATCH v2 iproute2-next 5/5] ip: always print interface name in color Stephen Hemminger
2018-02-21 16:48 ` 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=b8c10b01-e8b2-fdd8-8ec4-97e39d962fa7@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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).