linux-kernel - Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line

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: <Zihb6tSWTF_an5gY@finisterre.sirena.org.uk>
Date: Wed, 24 Apr 2024 10:10:02 +0900
From: Mark Brown <broonie@...nel.org>
To: Jani Nikula <jani.nikula@...el.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	workflows@...r.kernel.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags
 after cutter '---' line

On Tue, Apr 23, 2024 at 05:30:49PM +0300, Jani Nikula wrote:

> The Cc's on the mailing list archive are harder to dig up, and do not
> accurately reflect the same information. A lot of patches get sent with
> more Cc's in the mail message than in the commit message.

These days with b4 and lore it's pretty straightforward, especially with
subsystems that include a message ID based link to the discussion when
applying the patch - you can just grab the original discussion with a b4
mbox command.  

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)