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]
Date:   Sat, 3 Jun 2023 18:06:59 +0200
From:   Willy Tarreau <w@....eu>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     James Seo <james@...iv.tech>, Jonathan Corbet <corbet@....net>,
        Kalle Valo <kvalo@...nel.org>, workflows@...r.kernel.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC] docs: process: Send patches 'To' maintainers and 'Cc' lists

Hi Randy,

On Sat, Jun 03, 2023 at 08:55:39AM -0700, Randy Dunlap wrote:
> It sounds to me like we should just prohibit (not allow) emails that
> don't have a To: recipient in them.

Also those without subjects, which seem to become increasingly frequent
and which used to exclusively be used by spam years ago.

> > To reduce ambiguity and eliminate this class of potential (albeit
> > tangential) issues, prescribe sending patches 'To' maintainers and
> > 'Cc' lists. While we're at it, strengthen the recommendation to use
> > scripts/get_maintainer.pl to find patch recipients, and move Andrew
> > Morton's callout as the maintainer of last resort to the next
> > paragraph for better flow.
> > 
> 
> I think that is going overboard (too far). As long as a maintainer
> is a direct recipient of the email (patch), that should be sufficient.

Or it could be simplified, saying that all those who are expected to
play a role on the patchset (review, test, merge etc) should be in the
'To' field while those who might possibly be interested in having a
look are in 'Cc' (lists, other people having expressed interest in the
patchset, single-time contributors to the file being changed etc). It
could be hinted that usually people read mails sent to them faster than
those they're CCed. This implies that maintainers have to be in To and
lists in Cc.

regards,
Willy

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ