From: Stephen Hemminger <stephen@networkplumber.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
dsahern@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] genl: print caps for all families
Date: Fri, 24 Feb 2023 14:33:27 -0800 [thread overview]
Message-ID: <20230224143327.4221f8a5@hermes.local> (raw)
In-Reply-To: <20230224102935.591dbb43@kernel.org>
On Fri, 24 Feb 2023 10:29:35 -0800
Jakub Kicinski <kuba@kernel.org> wrote:
> On Fri, 24 Feb 2023 12:47:02 -0500 Jamal Hadi Salim wrote:
> > On Fri, Feb 24, 2023 at 12:11 PM Jakub Kicinski <kuba@kernel.org> wrote:
> > > On Thu, 23 Feb 2023 19:27:42 -0800 Stephen Hemminger wrote:
> > > > What about JSON support. Is genl not json ready yet?
> > >
> > > All the genl code looks quite dated, no JSON anywhere in sight :(
> >
> > We'll take care of this...
>
> I'm biased but at this point the time is probably better spent trying
> to filling the gaps in ynl than add JSON to a CLI tool nobody knows
> about... too harsh? :
So I can drop it (insert sarcasm here)
next prev parent reply other threads:[~2023-02-24 22:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 1:52 [PATCH iproute2] genl: print caps for all families Jakub Kicinski
2023-02-24 1:57 ` Jakub Kicinski
2023-02-24 8:33 ` Johannes Berg
2023-02-24 15:15 ` Jamal Hadi Salim
2023-02-24 15:22 ` Jamal Hadi Salim
2023-02-24 17:10 ` Jakub Kicinski
2023-02-24 17:46 ` Jamal Hadi Salim
2023-02-24 18:30 ` Jakub Kicinski
2023-02-24 3:27 ` Stephen Hemminger
2023-02-24 17:11 ` Jakub Kicinski
2023-02-24 17:47 ` Jamal Hadi Salim
2023-02-24 18:29 ` Jakub Kicinski
2023-02-24 22:33 ` Stephen Hemminger [this message]
2023-02-25 0:56 ` Jakub Kicinski
2023-02-25 17:21 ` Jamal Hadi Salim
-- strict thread matches above, loose matches on Subject: below --
2023-02-25 0:37 Jakub Kicinski
2023-02-25 16:41 ` Jamal Hadi Salim
2023-03-04 2:20 ` patchwork-bot+netdevbpf
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=20230224143327.4221f8a5@hermes.local \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=jhs@mojatatu.com \
--cc=kuba@kernel.org \
--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).