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: <Zifl5PAAD1GTLWSK@smile.fi.intel.com>
Date: Tue, 23 Apr 2024 19:46:28 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Jonathan Corbet <corbet@....net>
Cc: Jani Nikula <jani.nikula@...el.com>, workflows@...r.kernel.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags
 after cutter '---' line

On Tue, Apr 23, 2024 at 08:44:24AM -0600, Jonathan Corbet wrote:
> Andy Shevchenko <andriy.shevchenko@...ux.intel.com> writes:
> 
> >> A lot of patches get sent with
> >> more Cc's in the mail message than in the commit message.
> >
> > Note, this is the recommendation as it's stated. You can continue polluting
> > the environment on your wish.
> 
> The environmental case here is ... not strong.
> 
> I, too, have my doubts about this recommendation; responding this way is
> not going to change a lot of minds, IMO.

Let's see how discussion will go.

Nevertheless, there seem no objections against the first patch in the series.
Can it be applied?

-- 
With Best Regards,
Andy Shevchenko