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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiuR7_A=PbN8jhmqGPJQHypUHR+W4-UuSVhOVWvYXs1Tg@mail.gmail.com>
Date: Wed, 26 Jul 2023 11:59:04 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: 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, 26 Jul 2023 at 11:48, Jakub Kicinski <kuba@...nel.org> wrote:
>
> We get at least one fix a week where author adds a Fixes tag
> but somehow magically didn't CC the author of that commit.
> When we ask they usually reply with "but I run get_maintainer -f,
> isn't that what I'm supposed to do?".

Bah. I think you're blaming entirely the wrong people, and the wrong tool.

Your complaint seems to be "we got a fix, it even says what commit it
is fixing, and the tool that the person ran didn't add the right
people automatically".

And my reaction is "I use that tooling, I want it to do exactly what
it does right now, why are you blaming that tool"?

You're already using 'patchwork'. Why don't you instead go "Oh, *that*
tool isn't doing the right thing?"

                  Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ