[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b31fb954-a9ee-e039-9f44-9fb8daec54dd@gmail.com>
Date: Tue, 6 Mar 2018 16:51:20 -0700
From: David Ahern <dsahern@...il.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: netdev@...r.kernel.org, Stephen Hemminger <sthemmin@...rosoft.com>
Subject: Re: [PATCH iproute2-next v2 00/12] ip more JSON
On 3/6/18 2:07 PM, Stephen Hemminger wrote:
> From: Stephen Hemminger <sthemmin@...rosoft.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.
Powered by blists - more mailing lists