From: Jakub Kicinski <kuba@kernel.org>
To: David Ahern <dsahern@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>, Joe Damato <jdamato@fastly.com>,
Stephen Hemminger <stephen@networkplumber.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: yaml gen NL families support in iproute2?
Date: Mon, 28 Oct 2024 15:15:34 -0700 [thread overview]
Message-ID: <20241028151534.1ef5cbb5@kernel.org> (raw)
In-Reply-To: <845f8156-e7f5-483f-9e07-439808bde7a2@kernel.org>
On Mon, 28 Oct 2024 15:29:35 -0600 David Ahern wrote:
> On 10/28/24 2:58 PM, Jakub Kicinski wrote:
> > I was hoping for iproute2 integration a couple of years ago, but
> > David Ahern convinced me that it's not necessary. Apparently he
> > changed his mind now, but I remain convinced that packaging
> > YNL CLI is less effort and will ensure complete coverage with
> > no manual steps.
>
> I not recall any comment about it beyond cli.py in its current form
> is a total PITA to use as it lacks help and a man page.
I can only find this thread now:
https://lore.kernel.org/all/20240302193607.36d7a015@kernel.org/
Could be a misunderstanding, but either way, documenting an existing
tool seems like strictly less work than recreating it from scratch.
next prev parent reply other threads:[~2024-10-28 22:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 17:41 yaml gen NL families support in iproute2? Paolo Abeni
2024-10-17 18:36 ` David Ahern
2024-10-21 20:58 ` Joe Damato
2024-10-22 7:55 ` Paolo Abeni
2024-10-28 20:58 ` Jakub Kicinski
2024-10-28 21:29 ` David Ahern
2024-10-28 22:15 ` Jakub Kicinski [this message]
2024-10-28 23:40 ` Stephen Hemminger
2024-10-29 0:06 ` Jakub Kicinski
2024-10-29 0:43 ` Stephen Hemminger
2024-10-29 9:29 ` Paolo Abeni
2024-10-29 13:39 ` Jakub Kicinski
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=20241028151534.1ef5cbb5@kernel.org \
--to=kuba@kernel.org \
--cc=dsahern@kernel.org \
--cc=jdamato@fastly.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.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).