From: Jakub Kicinski <kuba@kernel.org>
To: Jan Stancek <jstancek@redhat.com>
Cc: Donald Hunter <donald.hunter@gmail.com>,
stfomichev@gmail.com, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/5] tools: ynl: provide symlinks to user-facing scripts for compatibility
Date: Wed, 11 Dec 2024 18:13:42 -0800 [thread overview]
Message-ID: <20241211181342.31676ec4@kernel.org> (raw)
In-Reply-To: <CAASaF6wcW54MwR-CdR_bfXRJS+ar0y87g7FN1_T6qLVJX0Ti6A@mail.gmail.com>
On Wed, 11 Dec 2024 13:42:28 +0100 Jan Stancek wrote:
> > > Did someone ask for this? Does everything work without the symlinks?
> > > If the answers are "no", "yes" then let's try without this patch.
> > > In tree users should be able to adjust.
> >
> > I asked for the symlinks for cli.py and ethtool.py to avoid surprising
> > people when they move. The ynl-gen- scripts are primarily used in-tree
> > via Makefiles so I didn't think they should be symlinked. Happy to go
> > with your suggestion to drop this if you'd prefer not to have any
> > symlinks.
>
> I'll drop them, we can always add them later in case someone
> _really_ needs original script locations.
FWIW that's my thinking, too.
next prev parent reply other threads:[~2024-12-12 2:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 14:47 [PATCH v2 0/5] tools: ynl: add install target Jan Stancek
2024-12-09 14:47 ` [PATCH v2 1/5] tools: ynl: move python code to separate sub-directory Jan Stancek
2024-12-09 14:47 ` [PATCH v2 2/5] tools: ynl: provide symlinks to user-facing scripts for compatibility Jan Stancek
2024-12-11 3:26 ` Jakub Kicinski
2024-12-11 9:21 ` Donald Hunter
2024-12-11 12:42 ` Jan Stancek
2024-12-12 2:13 ` Jakub Kicinski [this message]
2024-12-09 14:47 ` [PATCH v2 3/5] tools: ynl: add initial pyproject.toml for packaging Jan Stancek
2024-12-09 14:47 ` [PATCH v2 4/5] tools: ynl: add install target for specs and docs Jan Stancek
2024-12-11 3:31 ` Jakub Kicinski
2024-12-09 14:47 ` [PATCH v2 5/5] tools: ynl: add main install target Jan Stancek
2024-12-09 21:30 ` Joe Damato
2024-12-10 13:56 ` Jan Stancek
2024-12-10 16:34 ` Joe Damato
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=20241211181342.31676ec4@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stfomichev@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).