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: <20230726-yeah-acrobat-ba1acf@meerkat>
Date: Wed, 26 Jul 2023 20:33:16 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, 
	Joe Perches <joe@...ches.com>, 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, 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, then I think
the need for this check goes away. The submitter can then just worry about
getting *everything else* right about the patch and not worry about who to add
into Cc's.

-K

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ