linux-kernel - Re: [PATCH v4] media: Documentation: Improve grammar in DVB API

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <DB8S4WLTG1SS.NVODTL6KNFXF@brighamcampbell.com>
Date: Thu, 10 Jul 2025 17:55:47 -0600
From: "Brigham Campbell" <me@...ghamcampbell.com>
To: "David Hunter" <david.hunter.linux@...il.com>,
 Hanne-Lotta Mäenpää <hannelotta@...il.com>,
 <mchehab@...nel.org>
Cc: <linux-media@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
 <linux-kernel-mentees@...ts.linux.dev>, <skhan@...uxfoundation.org>
Subject: Re: [PATCH v4] media: Documentation: Improve grammar in DVB API

On Wed Jul 9, 2025 at 10:22 PM MDT, David Hunter wrote:
> On 7/8/25 11:52, Hanne-Lotta Mäenpää wrote:
>> Fix typos and punctuation and improve grammar in documentation.
>> 
>> Signed-off-by: Hanne-Lotta Mäenpää <hannelotta@...il.com>
>
> Overall, good work. Here is a suggestion for future patch series:
>
> Subsequent versions of patch series should be posted as replies in the same thread. Currently, each version is its own independent thread, which makes it hard to track changes. This link has the documentation for the proper way to handle subsequent patches:
>
> https://www.kernel.org/pub/software/scm/git/docs/SubmittingPatches.html
>
> The relevant part starts at "To that end, send them as replies to either..."

This documentation you've linked is specific to git, not the linux
kernel.

The kernel documentation argues against doing what you suggest [1]: "for
a multi-patch series, it is generally best to avoid using In-Reply-To:
to link to older versions of the series. This way multiple versions of
the patch don’t become an unmanageable forest of references in email
clients."

[1]: https://www.kernel.org/doc/html/latest/process/submitting-patches.html

>
> Another good practice is to have the previous versions' links from "lore.kernel.org" directly in the change log. 
>
> Thanks, 
> David Hunter

Nice work, as usual, Hanne-Lotta.

Brigham