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] [day] [month] [year] [list]
Message-ID: <6b872eb0-22ca-408e-9c4e-8f094c3580ae@gmail.com>
Date: Fri, 11 Jul 2025 20:05:51 +0300
From: Hanne-Lotta Mäenpää <hannelotta@...il.com>
To: Brigham Campbell <me@...ghamcampbell.com>,
 David Hunter <david.hunter.linux@...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

Hello,

On 7/11/25 2:55 AM, Brigham Campbell wrote:
> 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
> 

Right, that clears it up. On a closer look, the URL indicates which 
documentation is for git development.

> 
> Nice work, as usual, Hanne-Lotta.
> 
> Brigham
> 

I really appreciate this comment. Thank you for your encouragement!

Best regards,

Hanne-Lotta Mäenpää


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ