mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Matthew Garrett <matthew.garrett@nebula.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove unnecessarily gendered language
Date: Thu, 5 Dec 2013 11:48:08 +0100	[thread overview]
Message-ID: <20131205104808.GA6455@amd.pavel.ucw.cz> (raw)
In-Reply-To: <1386033532-25431-1-git-send-email-matthew.garrett@nebula.com>

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?

I don't think this makes documentation better.

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

(And I'm pretty sure most people will parse it the wrong way.)

> @@ -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?


NAK, FWIW.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2013-12-05 10:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03  1:18 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 [this message]
2013-12-05 16:35   ` Matthew Garrett
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=20131205104808.GA6455@amd.pavel.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.garrett@nebula.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

all inboxes | Powered by JetHome®