From: David Ahern <dsahern@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH iproute2-next v2 00/12] ip more JSON
Date: Tue, 6 Mar 2018 16:51:20 -0700 [thread overview]
Message-ID: <b31fb954-a9ee-e039-9f44-9fb8daec54dd@gmail.com> (raw)
In-Reply-To: <20180306210720.19802-1-stephen@networkplumber.org>
On 3/6/18 2:07 PM, Stephen Hemminger wrote:
> From: Stephen Hemminger <sthemmin@microsoft.com>
>
> The ip command implementation of JSON was very spotty. Only address
> and link were originally implemented. After doing route for next,
> went ahead and implemented it for a bunch of the other sub commands.
>
> Hopefully will reach full coverage soon.
>
> Stephen Hemminger (12):
> ipneigh: add color and json support
> ipaddrlabel: add json support
> iprule: add json support
> ipntable: add json support
> ipnetconf: add JSON support
> tcp_metrics; make tables const
> tcp_metrics: add json support
> ipsr: add json support
> token: support JSON
> tuntap: support JSON output
> fou: break long lines
> fou: support JSON output
>
applied to iproute2-next.
glad to see the json support. Thanks for working on it.
prev parent reply other threads:[~2018-03-06 23:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 21:07 [PATCH iproute2-next v2 00/12] ip more JSON Stephen Hemminger
2018-03-06 21:07 ` [PATCH iproute2-next v2 01/12] ipneigh: add color and json support Stephen Hemminger
2018-03-06 21:07 ` [PATCH iproute2-next v2 02/12] ipaddrlabel: add " Stephen Hemminger
2018-03-06 21:07 ` [PATCH iproute2-next v2 03/12] iprule: " Stephen Hemminger
2018-03-06 21:07 ` [PATCH iproute2-next v2 04/12] ipntable: " Stephen Hemminger
2018-03-06 21:07 ` [PATCH iproute2-next v2 05/12] ipnetconf: add JSON support Stephen Hemminger
2018-03-06 21:07 ` [PATCH iproute2-next v2 06/12] tcp_metrics; make tables const Stephen Hemminger
2018-03-06 21:07 ` [PATCH iproute2-next v2 07/12] tcp_metrics: add json support Stephen Hemminger
2018-03-06 21:07 ` [PATCH iproute2-next v2 08/12] ipsr: " Stephen Hemminger
2018-03-06 21:07 ` [PATCH iproute2-next v2 09/12] token: support JSON Stephen Hemminger
2018-03-06 21:07 ` [PATCH iproute2-next v2 10/12] tuntap: support JSON output Stephen Hemminger
2018-03-06 21:07 ` [PATCH iproute2-next v2 11/12] fou: break long lines Stephen Hemminger
2018-03-06 21:07 ` [PATCH iproute2-next v2 12/12] fou: support JSON output Stephen Hemminger
2018-03-06 23:51 ` 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=b31fb954-a9ee-e039-9f44-9fb8daec54dd@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).