public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <matthew.garrett@nebula.com>
To: "pavel@ucw.cz" <pavel@ucw.cz>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove unnecessarily gendered language
Date: Thu, 5 Dec 2013 16:35:15 +0000	[thread overview]
Message-ID: <1386261314.14035.8.camel@x230> (raw)
In-Reply-To: <20131205104808.GA6455@amd.pavel.ucw.cz>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2383 bytes --]

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@nebula.com>
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2013-12-05 16:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03  1:18 [PATCH] Remove unnecessarily gendered language Matthew Garrett
2013-12-03  9:04 ` Geert Uytterhoeven
2013-12-03 17:53   ` Randy Dunlap
2013-12-04  2:36   ` Matthew Garrett
2013-12-05 10:48 ` Pavel Machek
2013-12-05 16:35   ` Matthew Garrett [this message]
2013-12-08 12:38     ` Pavel Machek
2013-12-09 19:09       ` Matthew Garrett
2013-12-10  7:56         ` Oliver Neukum
2013-12-05 16:54   ` One Thousand Gnomes
2013-12-05 17:41     ` Harald Arnesen
2013-12-08 12:47     ` Pavel Machek
2013-12-18 13:53 ` Mark Brown

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=1386261314.14035.8.camel@x230 \
    --to=matthew.garrett@nebula.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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