From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Kees Cook <kees@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Ruben Sutton <ruben@scstudios.tech>,
linux-doc@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
workflows@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [PATCH] docs: process: use gender-neutral pronouns
Date: Thu, 10 Sep 2026 12:49:58 +0300 [thread overview]
Message-ID: <20260910094958.GI1892234@killaraus.ideasonboard.com> (raw)
In-Reply-To: <6e4cb304-fc9c-4cd8-bd6d-2d0dd635f3cf@leemhuis.info>
On Thu, Sep 10, 2026 at 08:59:04AM +0200, Thorsten Leemhuis wrote:
> On 9/9/26 20:47, Kees Cook wrote:
> > On Wed, Sep 09, 2026 at 09:14:04AM -0600, Jonathan Corbet wrote:
> >> Ruben Sutton writes:
> >>
> >>> Several process documents use gendered pronouns when referring
> >>> generically to developers and maintainers. Use singular they instead,
> >>> making the language inclusive without changing its meaning.
> >>>
> >>> Leave pronouns referring to named people and text in attributed
> >>> quotations unchanged.
> >>
> >> Ouch.
> >>
> >> I have no objection in principle to this change, but if we try to clean
> >> up the whole kernel in this way we're going to have a *lot* of churn
> >> and, undoubtedly, some unpleasant discussions at some point.
> >>
> >> I'm tempted to raise this question at the maintainers summit to see if I
> >> can get some sort of project-wide policy laid out.
> >
> > FWIW, I'd agree "indefinite they" (or "singular they") is the right
> > language here: "his or her" is both annoying to read (too many words)
> > and non-inclusive. Using "their" solves both.
> I do, too.
>
> But all this makes me wonder: In case we decide to go down that route,
> how do we prevent gendered pronouns from accidentally sneaking back in,
> for example, through subsystems that change their docs directly? Do we
> maybe have something already somewhere that watches changes to
> Documentation/ where we could plug in a test script that yells if it
> detects this in next? And yes, obviously someone would then also need to
> write such a script.
This appears to me as similar to the words we decided to ban in commit
a5f526ecb075 ("CodingStyle: Inclusive Terminology"). As far as I'm
aware, there's no tooling to enforce this, we instead rely on reviewers
(and authors in the first place of course) knowing the rules. The
inclusive terminology discussion that occurred back then made the news,
helping us to raise awareness of the rules. For gender-neutral pronouns
we may need to communicate a bit more proactively towards at least
subsystem maintainers.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2026-09-10 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 14:41 Ruben Sutton
2026-09-09 15:14 ` Jonathan Corbet
2026-09-09 18:47 ` Kees Cook
2026-09-10 6:59 ` Thorsten Leemhuis
2026-09-10 9:49 ` Laurent Pinchart [this message]
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=20260910094958.GI1892234@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=corbet@lwn.net \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=rdunlap@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=ruben@scstudios.tech \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/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®