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] [day] [month] [year] [list]
Message-ID: <13fd63b7e8e0f197842ae1f1264e50c9614d0667.camel@perches.com>
Date: Thu, 04 Jan 2024 16:34:10 -0800
From: Joe Perches <joe@...ches.com>
To: Anthony LOISEAU <anthony.loiseau@...circuits.com>, 
	"linux-kernel@...r.kernel.org"
	 <linux-kernel@...r.kernel.org>
Subject: Re: get_maintainer.pl: penguin chiefs, maintainers and the rest

On Wed, 2024-01-03 at 16:12 +0000, Anthony LOISEAU wrote:
> Hello,

Hello Anthony.


> I am a little bit cluttered about a few things around
> get_maintainer.pl and the fact that penguin chiefs may also be
> maintainers, at least in third party projects also using
> get_maintainer.pl script. My feeling is that get_maintainer.pl
> mishandles penguin chiefs without it being an issue for Linux case,

[]
> My feeling is that this would be the cleaner way to address this
> issue. What is you opinion?mmm

For the various modified versions of get_maintainer.pl
for other projects, any change should be made there.

I think the linux specific get_maintainer.pl works as-is
and does not particularly need modification.

An option might be to externalize the 'penguin-chief'
block into something like a separate file that is parsed
at initialization.

Maybe with a rename as penguin_chief is generally Tux,
umm Torvalds...

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ