From: Stephen Hemminger <stephen@networkplumber.org>
To: Alexis Vachette <avachette@deezer.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] stats output
Date: Fri, 30 Nov 2018 11:55:20 -0800 [thread overview]
Message-ID: <20181130115520.12abea3b@xeon-e3> (raw)
In-Reply-To: <CAP962rREvFEjKTVfVxNDAjAej8UkARCNQBji6UTr3_ujDjzTJQ@mail.gmail.com>
On Fri, 30 Nov 2018 20:22:35 +0100
Alexis Vachette <avachette@deezer.com> wrote:
> Hi Stephen,
>
> Thanks for your kind reply.
>
> It's sad to hear that, I am aware of your concern too.
>
> But it's not the best behavior for a network engineer.
>
> Is it possible to add a new option or everything is stone graved ?
You can add new options at will as long as they don't conflict with existing
usage (and you update the man page). JSON and colorized output were added
in the last years.
Note: the iproute options are definitely a hodge-podge collection, the code doesn't
follow the typical Linux style of using getopt and getopt_long, and has a bit of
network OS model as well.
What are you thinking of.
prev parent reply other threads:[~2018-12-01 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 13:33 [PATCH iproute2] stats output Alexis Vachette
2018-11-30 18:12 ` Stephen Hemminger
2018-11-30 18:26 ` Roopa Prabhu
2018-11-30 18:31 ` David Ahern
2018-11-30 19:22 ` Alexis Vachette
2018-11-30 19: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=20181130115520.12abea3b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=avachette@deezer.com \
--cc=netdev@vger.kernel.org \
/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).