[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y6iRYO5+cIo5exxu@electric-eye.fr.zoreil.com>
Date: Sun, 25 Dec 2022 19:07:28 +0100
From: Francois Romieu <romieu@...zoreil.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "Mogilappagari, Sudheer" <sudheer.mogilappagari@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"mkubecek@...e.cz" <mkubecek@...e.cz>,
"andrew@...n.ch" <andrew@...n.ch>,
"corbet@....net" <corbet@....net>,
"Samudrala, Sridhar" <sridhar.samudrala@...el.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@...el.com>,
stephen@...workplumber.org
Subject: Re: [PATCH ethtool-next v2 2/2] netlink: add netlink handler for get
rss (-x)
Jakub Kicinski <kuba@...nel.org> :
> On Fri, 23 Dec 2022 12:08:16 +0100 Francois Romieu wrote:
[...]
> > 'ip' json output does not use the suggested format.
> >
> > It may be interesting to know if the experience proved it to be
> > a poor choice.
>
> Hopefully without sounding impolite let me clarify that it is precisely
> *experience* using the JSON output of ip extensively in Python and Ruby
> (chef) which leads me to make the suggestion.
Thank you for the explanation.
While misguided, I've always worked under the assumption that JSON could
also be looked at (especially when tools take care of indenting it).
Knowing that there is a strict "JSON as an interchange format only" policy
and that apparent lack of consistency may be seen as the legacy of mistaken
choices is an helpful hint.
So, no place for hexadecimal, yes.
--
Ueimor
Powered by blists - more mailing lists