From: Stephen Hemminger <stephen@networkplumber•org>
To: netdev@vger•kernel.org
Cc: Stephen Hemminger <stephen@networkplumber•org>
Subject: [PATCH iproute2-next 0/4] bridge: json and color output
Date: Sun, 18 Feb 2018 19:18:14 -0800 [thread overview]
Message-ID: <20180219031818.25797-1-stephen@networkplumber.org> (raw)
This set of patches adds color and full JSON support to bridge command.
It also aligns ths output format and command line options to match
ip command; this is a change that may impact those using "compress vlan"
option or doing screen scraping.
The JSON output also changes slightly. But this should not impact
any real user, because in several cases the current format was
invalid JSON!
Stephen Hemminger (4):
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
bridge/br_common.h | 5 +-
bridge/bridge.c | 16 ++-
bridge/fdb.c | 279 ++++++++++++++++-------------------------
bridge/link.c | 304 +++++++++++++++++++++++++++------------------
bridge/mdb.c | 354 ++++++++++++++++++++++-------------------------------
bridge/vlan.c | 280 ++++++++++++++++--------------------------
man/man8/bridge.8 | 15 ++-
7 files changed, 574 insertions(+), 679 deletions(-)
--
2.16.1
next reply other threads:[~2018-02-19 3:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 3:18 Stephen Hemminger [this message]
2018-02-19 3:18 ` [PATCH iproute2-next 1/4] bridge: implement json pretty print flag Stephen Hemminger
2018-02-19 22:24 ` Serhey Popovych
2018-02-20 19:17 ` Stephen Hemminger
2018-02-19 3:18 ` [PATCH iproute2-next 2/4] bridge: colorize output and use JSON print library Stephen Hemminger
2018-02-19 3:18 ` [PATCH iproute2-next 3/4] bridge: add json support for link command Stephen Hemminger
2018-02-19 3:18 ` [PATCH iproute2-next 4/4] bridge: update man page for new color and json changes Stephen Hemminger
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=20180219031818.25797-1-stephen@networkplumber.org \
--to=stephen@networkplumber$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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