From: Jonathan Corbet <corbet@lwn.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH] docs: submitting-patches: adjust Fixes definition slightly
Date: Tue, 09 Sep 2025 13:42:54 -0600 [thread overview]
Message-ID: <87cy7zv2dd.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250904144533.2146576-1-kuba@kernel.org>
Jakub Kicinski <kuba@kernel.org> writes:
> Every now and then people send stylistic patches and use Fixes
> purely to refer to a commit which added the ugly or unnecessary
> code. Reword the docs about Fixes.
>
> It should hopefully be enough to lead with the word "bug"
> rather than "issue". We can add more verbiage later, tho, let's
> try the word swap first. I always feel like the more words the
> smaller the chance someone will actually read the docs.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> Documentation/process/submitting-patches.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
You are an optimist :)
I've applied this, thanks.
jon
prev parent reply other threads:[~2025-09-09 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 14:45 [PATCH] docs: submitting-patches: adjust Fixes definition slightly Jakub Kicinski
2025-09-09 19:42 ` Jonathan Corbet [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=87cy7zv2dd.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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