From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 2/3] MAINTAINERS: record known Git Lab handles for all maintainers
Date: Wed, 24 Jun 2026 13:30:42 +0100 [thread overview]
Message-ID: <ajvN8nluiWdpeI3t@redhat.com> (raw)
In-Reply-To: <55d966a8-7698-421a-8265-2235d5fe104a@oss.qualcomm.com>
On Mon, Jun 22, 2026 at 10:36:43PM +0200, Philippe Mathieu-Daudé wrote:
> Hi Daniel,
>
> On 22/6/26 13:31, Daniel P. Berrangé wrote:
> > This updates MAINTAINERS with a "G:" line corresponding to every
> > "M:" line that can be identified with a match against
> >
> > https://gitlab.com/qemu-project/qemu/-/project_members
> >
> > This update was done using a largely automated process based on
> > the data extracted with
> >
> > $ glab api --paginate /projects/qemu-project%2fqemu/members | jq -c '.[] | {username, name}'
> > $ glab api --paginate /groups/qemu-project/members | jq -c '.[] | {username, name}'
> >
> > Some Git Lab accounts had real names that didn't have an exact
> > match in MAINTAINERS so the glab api data was manually pre-processed
> > to change those names.
> >
> > A Perl script was then used to insert "G:" lines for every "M:"
> > lines.
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > MAINTAINERS | 332 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 332 insertions(+)
> > @@ -84,13 +92,16 @@ Responsible Disclosure, Reporting Security Issues
> > -------------------------------------------------
> > W: https://wiki.qemu.org/SecurityProcess
> > M: Michael S. Tsirkin <mst@redhat.com>
> > +G: @mstredhat
> > L: qemu-security@nongnu.org
> > Trivial patches
> > ---------------
> > Trivial patches
> > M: Michael Tokarev <mjt@tls.msk.ru>
> > +G: @mjt0k
> > M: Laurent Vivier <laurent@vivier.eu>
> > +G: @lvivier
> > S: Maintained
> > L: qemu-trivial@nongnu.org
> > K: ^Subject:.*(?i)trivial
>
> This is an approach, and it does the job, but I'm worried about its
> maintainability. Since there is 1 handle per email, what about a
> .gitlabmap similar to .mailmap, a key:value mail:gitlab handle?
I've sent a v2 which tries this approach and I think it is somewhat
nicer.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-06-24 12:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 11:31 [PATCH 0/3] Record maintainer/reviewer Git Lab handles Daniel P. Berrangé
2026-06-22 11:31 ` [PATCH 1/3] get_maintainer: add ability to report Git Lab handle Daniel P. Berrangé
2026-06-22 11:31 ` [PATCH 2/3] MAINTAINERS: record known Git Lab handles for all maintainers Daniel P. Berrangé
2026-06-22 15:43 ` Alex Bennée
2026-06-22 20:36 ` Philippe Mathieu-Daudé
2026-06-24 12:30 ` Daniel P. Berrangé [this message]
2026-06-23 23:30 ` Bin Meng
2026-06-22 11:31 ` [PATCH 3/3] MAINTAINERS: record known Git Lab handles for all reviewers Daniel P. Berrangé
2026-06-22 12:39 ` [PATCH 0/3] Record maintainer/reviewer Git Lab handles Fabiano Rosas
2026-06-22 14:17 ` Aditya Gupta
2026-06-23 15:40 ` Tao Tang
2026-06-24 4:40 ` Gautam Menghani
2026-06-24 4:46 ` Pierrick Bouvier
2026-06-24 4:48 ` Yonggang Luo
2026-06-24 12:39 ` Chao Liu
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=ajvN8nluiWdpeI3t@redhat.com \
--to=berrange@redhat.com \
--cc=philmd@oss.qualcomm.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.