From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>,
Manuel Ebner <manuelebnerli@mailbox.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] docs: verify/bisect: fix typos
Date: Thu, 03 Sep 2026 07:03:08 -0600 [thread overview]
Message-ID: <87zexy7aib.fsf@trenco.lwn.net> (raw)
In-Reply-To: <e93cd824-4115-4bc1-a702-04f92794924e@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> On 9/3/26 10:22, Manuel Ebner wrote:
>> On Wed, 2026-09-02 at 18:30 +0200, Thorsten Leemhuis wrote:
>>> On 9/2/26 13:51, Manuel Ebner wrote:
>
>>> For typos and grammar fixes there is not much to say, so maybe just
>>> state that; but you might want to look at a few recent changes in
>>> Documentation/ to see how other developers approach a situation like this.
>>
>> That's a good idea. I did only find slightly more verbose than mine, eg:
>>> Fix 'hay attention' -> 'pay attention' in file.rst
>> or
>>> Replace "an a few" with "and a few" in
>>> Documentation/driver-api/media/drivers/zoran.rst.
>
> Yeah, maybe that slipped thought; and if it's just one or two fixes
> okayish, but after that a vague "Fix a few typos/mistakes/grammer
> issues" becomes better I'd say, unless there is something more to tell.
> Hopefully Jonathan agrees with this.
I do; repeating the specific typo fixes in the changelog is just
redundant. As always, the changelog should focus on the *why* of the
change.
jon
prev parent reply other threads:[~2026-09-03 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 11:51 [PATCH v2] docs: verify/bisect: fix typos Manuel Ebner
2026-09-02 16:30 ` Thorsten Leemhuis
2026-09-03 8:22 ` Manuel Ebner
2026-09-03 8:38 ` Thorsten Leemhuis
2026-09-03 13:03 ` 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=87zexy7aib.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=manuelebnerli@mailbox.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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