netdev - Re: [PATCH v2] scripts: get_maintainer: steer people away from using file paths

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: Wed, 26 Jul 2023 18:07:22 -0700
From: Joe Perches <joe@...ches.com>
To: Konstantin Ryabitsev <konstantin@...uxfoundation.org>, Jakub Kicinski
	 <kuba@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Krzysztof Kozlowski
 <krzysztof.kozlowski@...aro.org>, geert@...ux-m68k.org, 
 gregkh@...uxfoundation.org, netdev@...r.kernel.org,
 workflows@...r.kernel.org,  mario.limonciello@....com
Subject: Re: [PATCH v2] scripts: get_maintainer: steer people away from
 using file paths

On Wed, 2023-07-26 at 20:33 -0400, Konstantin Ryabitsev wrote:
> On Wed, Jul 26, 2023 at 05:27:58PM -0700, Jakub Kicinski wrote:
> > > Think as if instead of being Cc'd on patches, they got Bcc'd on them.
> > 
> > I was being crafty 'cause if the CC is present in the lore archive
> > our patchwork check would see it :] 
> > But cant just trust the automation and kill the check, then.
> 
> If we can get it working reliably and to everyone's satisfaction,

big if.  great concept though.

arch wide changes are different.
API changes are different.
staging patches are different.

It'll take a bit of settling and some special case handling
but I believe it'd work out quite well in long run to have a
patches@...r.kernel.org address front end that is a scripted
exploder to the appropriate maintainers, reviewers, mailing
lists etc.