From: Stephen Hemminger <stephen@networkplumber.org>
To: Vadim Kochan <vadim4j@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: iproute2 ss: Some thoughts about additional info output layout
Date: Wed, 14 Jan 2015 14:55:56 -0800 [thread overview]
Message-ID: <20150114145556.1d33c9d9@urahara> (raw)
In-Reply-To: <20150108221240.GA23636@angus-think.lan>
On Fri, 9 Jan 2015 00:12:40 +0200
Vadim Kochan <vadim4j@gmail.com> wrote:
> Hi,
>
> I think that current output of ss utility visually looks little weird
> when additional info options were specified, so I feel that a lot of
> yours will say that it will break existing scripts of ss output parsing
> but I will try, so thats how I think ss output would looks better in
> case if additionally info options were specified (I am not sure how it
> would looks in the email) :
The current output is pretty much unparseable for options with ss.
For a parseable output generating JSON would be much better, I did that for
a couple of utilities.
I see no problem with having a better human format.
prev parent reply other threads:[~2015-01-15 2:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 22:12 iproute2 ss: Some thoughts about additional info output layout Vadim Kochan
2015-01-14 14:57 ` [REMINDER] " Vadim Kochan
2015-01-14 22:55 ` Stephen Hemminger [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=20150114145556.1d33c9d9@urahara \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=vadim4j@gmail.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).