Received-SPF: pass (google.com: domain of linux-kernel+bounces-17399-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Message-ID: <13fd63b7e8e0f197842ae1f1264e50c9614d0667.camel@perches.com>
Subject: Re: get_maintainer.pl: penguin chiefs, maintainers and the rest
From: Joe Perches <joe@perches.com>
To: Anthony LOISEAU <anthony.loiseau@allcircuits.com>, 
	"linux-kernel@vger.kernel.org"
	 <linux-kernel@vger.kernel.org>
Date: Thu, 04 Jan 2024 16:34:10 -0800
In-Reply-To: <AS8PR07MB894183C6DE3473F23D5A046FF9602@AS8PR07MB8941.eurprd07.prod.outlook.com>
References: 
	<AS8PR07MB894183C6DE3473F23D5A046FF9602@AS8PR07MB8941.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
Precedence: bulk
MIME-Version: 1.0

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...