From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Cleber Rosa" <crosa@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"John Snow" <jsnow@redhat.com>
Subject: [RFC PATCH 0/9] for 11.0 conversion* of get_maintainers.pl to python
Date: Thu, 11 Dec 2025 18:01:23 +0000 [thread overview]
Message-ID: <20251211180132.3186564-1-alex.bennee@linaro.org> (raw)
*incomplete
I wanted to look at adding gitlab tags to MAINTAINERS and baulked
slightly at figuring out what I would need to change in the perl
script to cleanly handle it.
While we imported the perl script from the kernel I'm fairly sure we
don't use half the features it has and as us grey beards age out less
people will be willing to tweak it. Consider this a proof-of-concept
for discussion about if it is worth perusing this path.
It only supports the two main forms:
./scripts/get_maintainer.py -f path/to/file
./scripts/get_maintainer.py path/to/patch1 path/to/patch2 ...
But who needs more?
Future improvements could include some more detailed analysis in
conjugation with the repo to analysis:
- missing areas of coverage
- maintainer stats
Who knows maybe the kernel guys will want to import our script one day
;-)
Alex.
Alex Bennée (9):
MAINTAINERS: fix missing names
MAINTAINERS: fix libvirt entry
MAINTAINERS: regularise the status fields
scripts/get_maintainer.py: minimal argument parsing
scripts/get_maintainer.py: resolve the source path
scripts/get_maintainer.py: initial parsing of MAINTAINERS
scripts/get_maintainer.py: add support for -f
scripts/get_maintainer.py: add support reading patch files
gitlab: add a check-maintainers task
MAINTAINERS | 10 +-
.gitlab-ci.d/static_checks.yml | 9 +
scripts/get_maintainer.py | 356 +++++++++++++++++++++++++++++++++
3 files changed, 370 insertions(+), 5 deletions(-)
create mode 100755 scripts/get_maintainer.py
--
2.47.3
next reply other threads:[~2025-12-11 18:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 18:01 Alex Bennée [this message]
2025-12-11 18:01 ` [RFC PATCH 1/9] MAINTAINERS: fix missing names Alex Bennée
2025-12-11 18:01 ` [RFC PATCH 2/9] MAINTAINERS: fix libvirt entry Alex Bennée
2025-12-12 6:45 ` Philippe Mathieu-Daudé
2025-12-12 11:00 ` Alex Bennée
2025-12-12 11:12 ` Ján Tomko
2025-12-11 18:01 ` [RFC PATCH 3/9] MAINTAINERS: regularise the status fields Alex Bennée
2025-12-12 6:43 ` Philippe Mathieu-Daudé
2025-12-11 18:01 ` [RFC PATCH 4/9] scripts/get_maintainer.py: minimal argument parsing Alex Bennée
2025-12-11 18:01 ` [RFC PATCH 5/9] scripts/get_maintainer.py: resolve the source path Alex Bennée
2025-12-11 18:01 ` [RFC PATCH 6/9] scripts/get_maintainer.py: initial parsing of MAINTAINERS Alex Bennée
2025-12-11 18:01 ` [RFC PATCH 7/9] scripts/get_maintainer.py: add support for -f Alex Bennée
2025-12-11 18:01 ` [RFC PATCH 8/9] scripts/get_maintainer.py: add support reading patch files Alex Bennée
2025-12-11 18:01 ` [RFC PATCH 9/9] gitlab: add a check-maintainers task Alex Bennée
2025-12-12 8:15 ` [RFC PATCH 0/9] for 11.0 conversion* of get_maintainers.pl to python Daniel P. Berrangé
2025-12-12 11:00 ` Alex Bennée
2025-12-12 11:25 ` Peter Maydell
2025-12-12 11:27 ` Peter Maydell
2025-12-12 14:38 ` Markus Armbruster
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=20251211180132.3186564-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).