linux-kernel - Re: [PATCH] Remove unnecessarily gendered language

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: <1386261314.14035.8.camel@x230>
Date:	Thu, 5 Dec 2013 16:35:15 +0000
From:	Matthew Garrett <matthew.garrett@...ula.com>
To:	"pavel@....cz" <pavel@....cz>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Remove unnecessarily gendered language

On Thu, 2013-12-05 at 11:48 +0100, Pavel Machek wrote:
> On Mon 2013-12-02 20:18:52, Matthew Garrett wrote:
> > The kernel as a number of cases of gendered language. The majority of these
> > refer to objects that don't have gender in English, and so I've replaced
> > them with "it" and "its". Some refer to people (developers or users), and
> > I've replaced these with the singular "they" variant. Some are simply
> > typos that I've fixed up.
> 
> Why is this good idea?

Using "he" to refer to objects without gender is (with some exceptions)
incorrect in English, so that set should be uncontroversial. "He" is
usually considered acceptable when referring to an individual of unknown
gender, but so is "they". The latter version has the advantage of not
giving the impression that we believe all our users are male.

> > @@ -127,7 +127,7 @@ gid=
> >  umask=			Provide default owner, group, and access mode mask.
> >  			These options work as documented in mount(8).  By
> >  			default, the files/directories are owned by root and
> > -			he/she has read and write permissions, as well as
> > +			they have read and write permissions, as well as
> >  			browse permission for directories.  No one else has any
> >  			access permissions.  I.e. the mode on all files is by
> >  			default rw------- and for directories rwx------, a
> 
> So... we had unambiguous text "user has read and write permissions"
> and now you have to wonder if they refers to "user" or
> "files/directories".

Reasonable. I'll rework that.

> > @@ -23,7 +24,7 @@ Quota netlink interface
> >  When user exceeds a softlimit, runs out of grace time or reaches hardlimit,
> >  quota subsystem traditionally printed a message to the controlling terminal of
> >  the process which caused the excess. This method has the disadvantage that
> > -when user is using a graphical desktop he usually cannot see the message.
> > +when user is using a graphical desktop they usually cannot see the
> >  message.
> 
> Is this even correct english?

No, but it wasn't to begin with either. I mostly avoided more
significant changes because I didn't want to risk changing existing
meaning.

> NAK, FWIW.

Why?

-- 
Matthew Garrett <matthew.garrett@...ula.com>