From: Vlastimil Babka <vbabka@suse.cz>
To: Joe Perches <joe@perches.com>
Cc: workflows@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Thorsten Leemhuis <linux@leemhuis.info>,
Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, Vlastimil Babka <vbabka@suse.cz>
Subject: [PATCH 0/2] get_maintainer: report subsystem status separately from maintainer role
Date: Tue, 14 Jan 2025 09:57:53 +0100 [thread overview]
Message-ID: <20250114-b4-get_maintainer-v1-0-ecf40f0d032d@suse.cz> (raw)
The script currently uses the subystem's status (S: field) to change how
maintainers are reported. One prominent example is when the status is
Supported, the maintainers are reported as "(supporter:SUBSYSTEM)".
I have been confused myself in the past seeing "supporter" and have seen
somebody recently wondering what it means as well.
I have read the threads from 2022 that in the end resulted in adjusting
documentation only [1]. I very much agree with Ted's points about taking
the subsystem status and applying it to all maintainers being wrong [2].
The attempt to modify get_maintainer output was retracted after Joe
objected that the status becomes not reported at all [3]. This series
addresses that by reporting the status (unless it's the most common
Maintained one) as part of the subsystem name.
Given this new approach, the next logical step is to do the same also
for reporting reviewers and mailing lists. In fact, subsystems with an
Orphan status some catch-all mailing list and no maintainers, so the
"(orphan minder:SUBSYSTEM)" would never be currently reported by
get_maintainer. The second patch thus adds reporting the subsystem
status in the same way for lists (and reviewers).
Changes since RFC [4]
- keep the special handling for THE REST section ("chief penguin")
- added patch 2 for reviewers and mailing lists
- R-b on patch 1 from Kees
[1] https://lore.kernel.org/all/20221006162413.858527-1-bryan.odonoghue@linaro.org/
[2] https://lore.kernel.org/all/Yzen4X1Na0MKXHs9@mit.edu/
[3] https://lore.kernel.org/all/30776fe75061951777da8fa6618ae89bea7a8ce4.camel@perches.com/
[4] https://lore.kernel.org/all/20241213112921.180978-2-vbabka@suse.cz/
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
---
Vlastimil Babka (2):
get_maintainer: decouple subsystem status from maintainer role
get_maintainer: print subsystem status also for reviewers and lists
scripts/get_maintainer.pl | 68 ++++++++++++++++++++++++++---------------------
1 file changed, 38 insertions(+), 30 deletions(-)
---
base-commit: 40384c840ea1944d7c5a392e8975ed088ecf0b37
change-id: 20250114-b4-get_maintainer-cc3358be81c0
Best regards,
--
Vlastimil Babka <vbabka@suse.cz>
next reply other threads:[~2025-01-14 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 8:57 Vlastimil Babka [this message]
2025-01-14 8:57 ` [PATCH 1/2] get_maintainer: decouple subsystem status " Vlastimil Babka
2025-01-14 8:57 ` [PATCH 2/2] get_maintainer: print subsystem status also for reviewers and lists Vlastimil Babka
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=20250114-b4-get_maintainer-v1-0-ecf40f0d032d@suse.cz \
--to=vbabka@suse.cz \
--cc=bryan.odonoghue@linaro.org \
--cc=joe@perches.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=tytso@mit.edu \
--cc=workflows@vger.kernel.org \
/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