From: Sasha Levin <sashal@kernel.org>
To: Achill Gilgenast <achill@achill.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
Bagas Sanjaya <bagasdotme@gmail.com>, Kees Cook <kees@kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH] README: remove unnecessary comma in "System Administrator" section
Date: Sun, 15 Feb 2026 08:11:40 -0500 [thread overview]
Message-ID: <aZHGDN2hYyvDTCed@laps> (raw)
In-Reply-To: <20260215111156.77301-1-achill@achill.org>
On Sun, Feb 15, 2026 at 12:11:52PM +0100, Achill Gilgenast wrote:
>Commas before "and" are unnecessary if they are used in the same
>context, as it is here.
>
>Fixes: b9a565b3e4d8 ("README: restructure with role-based documentation and guidelines")
>Signed-off-by: Achill Gilgenast <achill@achill.org>
>---
> README | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/README b/README
>index e6549b2a7aac..947265bc64ac 100644
>--- a/README
>+++ b/README
>@@ -98,7 +98,7 @@ Maintain and stabilize kernel versions:
> System Administrator
> --------------------
>
>-Configure, tune, and troubleshoot Linux systems:
>+Configure, tune and troubleshoot Linux systems:
I suppose that this is a matter of preference, but the README consistently uses
the Oxford comma throught the text.
I think I'll just point to
https://docs.kernel.org/doc-guide/contributing.html#typo-fixes and defer this
to the Documentation maintainers :)
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-02-15 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 11:11 [PATCH] README: remove unnecessary comma in "System Administrator" section Achill Gilgenast
2026-02-15 13:11 ` Sasha Levin [this message]
2026-02-15 17:40 ` Randy Dunlap
2026-02-15 15:46 ` Jonathan Corbet
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=aZHGDN2hYyvDTCed@laps \
--to=sashal@kernel.org \
--cc=achill@achill.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=rdunlap@infradead.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