From: Jonathan Corbet <corbet@lwn.net>
To: Ruben Sutton <ruben@scstudios.tech>, linux-doc@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Thorsten Leemhuis <linux@leemhuis.info>,
workflows@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev, Ruben Sutton <ruben@scstudios.tech>
Subject: Re: [PATCH] docs: process: use gender-neutral pronouns
Date: Wed, 09 Sep 2026 09:14:04 -0600 [thread overview]
Message-ID: <87pkymlao3.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260909144100.78177-1-ruben@scstudios.tech>
Ruben Sutton <ruben@scstudios.tech> 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.
>
> Assisted-by: LLM
> Signed-off-by: Ruben Sutton <ruben@scstudios.tech>
> ---
> Documentation/process/2.Process.rst | 2 +-
> Documentation/process/5.Posting.rst | 2 +-
> Documentation/process/6.Followthrough.rst | 2 +-
> Documentation/process/handling-regressions.rst | 2 +-
> Documentation/process/howto.rst | 2 +-
> Documentation/process/submitting-patches.rst | 2 +-
> 6 files changed, 6 insertions(+), 6 deletions(-)
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.
Thanks,
jon
next prev parent reply other threads:[~2026-09-09 15:14 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 [this message]
2026-09-09 18:47 ` Kees Cook
2026-09-10 6:59 ` Thorsten Leemhuis
2026-09-10 9:49 ` Laurent Pinchart
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=87pkymlao3.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--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®