From: Joe Perches <joe@perches.com>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
corbet@lwn.net, linux@leemhuis.info,
konstantin@linuxfoundation.org, krzysztof.kozlowski@linaro.org,
linux-doc@vger.kernel.org, akiyks@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v4 1/2] get_maintainer: Print maintainer for S: Supported
Date: Tue, 04 Oct 2022 01:02:04 -0700 [thread overview]
Message-ID: <30776fe75061951777da8fa6618ae89bea7a8ce4.camel@perches.com> (raw)
In-Reply-To: <20221003162411.431774-2-bryan.odonoghue@linaro.org>
On Mon, 2022-10-03 at 17:24 +0100, Bryan O'Donoghue wrote:
> Throughout the documentation we make reference to maintainers as the people
> who ought to be mailed when sending patches.
>
> Right now get_maintainer.pl returns "supporter" for maintained files which
> are denoted "S: Supported".
As it should.
I think this patch is misguided and do not agree with the concept.
Either do away with the concept of S: Supported or use it.
As is, it merely hides the actual content of the MAINTAINERS file.
A reader of the MAINTAINERS file would still see the actual value.
Using other options of get_maintainer.pl like --sections would show
the actual content.
Other options would still show S:
>
> Update get_maintainer to output "maintainer" for "S: Supported" the
> differentiation between paid (v) non-paid maintainers doesn't impact who
> needs to be mailed for patch submissions.
[]
> diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl
[]
> @@ -1283,7 +1283,7 @@ sub get_maintainer_role {
>
> $role = lc($role);
> if ($role eq "supported") {
> - $role = "supporter";
> + $role = "maintainer";
> } elsif ($role eq "maintained") {
> $role = "maintainer";
> } elsif ($role eq "odd fixes") {
next prev parent reply other threads:[~2022-10-04 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 16:24 [PATCH RESEND v4 0/2] Fixup instructions around mailing recipients Bryan O'Donoghue
2022-10-03 16:24 ` [PATCH RESEND v4 1/2] get_maintainer: Print maintainer for S: Supported Bryan O'Donoghue
2022-10-04 8:02 ` Joe Perches [this message]
2022-10-04 8:33 ` Bryan O'Donoghue
2022-10-03 16:24 ` [PATCH RESEND v4 2/2] Documentation/process: Be more explicit about who to mail on patch submission Bryan O'Donoghue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30776fe75061951777da8fa6618ae89bea7a8ce4.camel@perches.com \
--to=joe@perches.com \
--cc=akiyks@gmail.com \
--cc=bryan.odonoghue@linaro.org \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®