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: <1b96e465-0922-4c02-b770-4b1f27bebeb8@lunn.ch>
Date: Thu, 27 Jul 2023 13:00:15 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc: Jakub Kicinski <kuba@...nel.org>,
	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

> Think as if instead of being Cc'd on patches, they got Bcc'd on them.

And how does reply work? I assume it would only go to those in To: or
Cc: ? Is there enough context in the headers in a reply for the system
to figure out who to Bcc: the reply to?

   Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ