lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220922083029.52524b21@hermes.local>
Date:   Thu, 22 Sep 2022 08:30:29 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Vladimir Oltean <vladimir.oltean@....com>
Cc:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        David Ahern <dsahern@...nel.org>, Andrew Lunn <andrew@...n.ch>,
        Vivien Didelot <vivien.didelot@...il.com>,
        Florian Fainelli <f.fainelli@...il.com>
Subject: Re: [PATCH v2 iproute2-next] ip link: add sub-command to view and
 change DSA master

On Thu, 22 Sep 2022 14:41:24 +0000
Vladimir Oltean <vladimir.oltean@....com> wrote:

> 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.

Because it is in the Coding Style it has been approved by the
Linux Kernel Technical Advisor Board.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ