From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Ahern <dsahern@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH v2 iproute2-next] ip link: add sub-command to view and change DSA master
Date: Thu, 22 Sep 2022 14:41:24 +0000 [thread overview]
Message-ID: <20220922144123.5z3wib5apai462q7@skbuf> (raw)
In-Reply-To: <20220921153349.0519c35d@hermes.local>
On Wed, Sep 21, 2022 at 03:33:49PM -0700, Stephen Hemminger wrote:
> There is no reason that words with long emotional history need to be used
> in network command.
>
> https://inclusivenaming.org/word-lists/
>
> https://inclusivenaming.org/word-lists/tier-1/
>
> I understand that you and others that live in different geographies may
> have different feelings about this. But the goal as a community to
> not use names and terms that may hinder new diverse people from
> being involved.
The Linux kernel community is centered around a technical goal rather
than political or emotional ones, and for this reason I don't think it's
appropriate to go here in many more details than this.
All I will say is that I have more things to do than time to do them,
and I'm not willing to voluntarily go even one step back about this and
change the UAPI names while the in-kernel data structures and the
documentation remain with the old names, because it's not going to stop
there, and I will never have time for this.
So until this becomes mandatory in some sort of official way, I'd like
to make use of the exception paragraph, which in my reading applies
perfectly to this situation, thank you.
next prev parent reply other threads:[~2022-09-22 14:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 16:51 [PATCH v2 iproute2-next] ip link: add sub-command to view and change DSA master Vladimir Oltean
2022-09-21 18:36 ` Stephen Hemminger
2022-09-21 18:38 ` Vladimir Oltean
2022-09-21 22:33 ` Stephen Hemminger
2022-09-22 14:41 ` Vladimir Oltean [this message]
2022-09-22 15:30 ` Stephen Hemminger
2022-09-22 15:42 ` Andrew Lunn
2022-09-22 18:43 ` Vladimir Oltean
2022-09-22 19:04 ` Stephen Hemminger
2022-09-22 19:36 ` Vladimir Oltean
2022-09-22 20:34 ` Andrew Lunn
2022-09-22 21:25 ` Florian Fainelli
2022-09-22 21:28 ` Vladimir Oltean
2022-09-22 21:30 ` Florian Fainelli
2022-09-22 21:40 ` Vladimir Oltean
2022-09-22 21:41 ` Andrew Lunn
2022-09-22 21:52 ` Vladimir Oltean
2022-09-21 22:41 ` Stephen Hemminger
2022-09-22 1:30 ` Andrew Lunn
2022-09-22 13:24 ` Jakub Kicinski
2022-09-22 15:27 ` Stephen Hemminger
2022-09-22 15:36 ` Florian Fainelli
2022-09-22 18:00 ` Vladimir Oltean
2022-09-22 19:30 ` Jakub Kicinski
2022-09-22 20:13 ` Vladimir Oltean
2022-09-22 20:28 ` Stephen Hemminger
2022-09-22 20:36 ` Vladimir Oltean
2022-09-22 21:28 ` Florian Fainelli
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=20220922144123.5z3wib5apai462q7@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=dsahern@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vivien.didelot@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