From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Fabiano Rosas" <farosas@suse.de>
Subject: Re: [PATCH v2 0/2] Record maintainer/reviewer Git Lab handles
Date: Wed, 24 Jun 2026 18:38:58 +0100 [thread overview]
Message-ID: <ajwWMj0_3pht2uZM@redhat.com> (raw)
In-Reply-To: <96b2433f-f2ef-4c68-84de-2ef3508d8809@oss.qualcomm.com>
On Wed, Jun 24, 2026 at 03:19:15PM +0200, Philippe Mathieu-Daudé wrote:
> On 24/6/26 14:29, Daniel P. Berrangé wrote:
> > When triaging GitLab issues, whether regular bugs or security
> > disclosures, we need to be able to assign suitable accounts.
> >
> > We can only assign Git Lab handles for accounts that are members
> > of the QEMU group, or QEMU repository with the "Reporter" role
> > or higher.
> >
> > Currently one needs to run 'get_maintainer.pl -f <file>' to get
> > the maintainer / reviewer names & emails, and then look in the
> > GitLab members page to see if there is a match.
> >
> > This simplifies that by including the GitLab handle alongside
> > the email addresses:
> >
> > The GitLab account handle -> real name mapping is stored in
> > separate files .gitlab-map-auto & .gitlab-map-manual to avoid
> > redundancy in the MAINTAINERS file. The former file is
> > auto-generated and catches 99% of the mappings, the latter is
> > for manual fixups.
> >
> > With this series applied as is, we get the following stats
> >
> > $ ./scripts/gitlab-map-check
> > Missing GitLab handle: Akihiko Odaki
...
> > Missing GitLab handle: zhenwei pi
> > Missing GitLab handle: Zhenzhong Duan
> > Missing GitLab handle: Zhuoying Cai
> > GitLab handles missing: 161 / present: 57
> >
> > Plenty of those will have GitLab accounts, but are simply not members
> > of QEMU. Plenty more probably aren't registered with GitLab at all.
> >
> > Short of emailing all of those people directly, I don't see a good
> > way to identify their GitLab accounts (if any), in order to invite
> > them to the QEMU project. I don't want to blindly invite accounts
> > which merely have the same name on GitLab as there's too much risk
> > of getting a mis-match.
...
> No clue why Hanna is listed here...
>
> Applying: gitlab: introduce files mapping GitLab accounts to real names
> Applying: get_maintainer: add ability to report Git Lab handle
> .git/rebase-apply/patch:121: trailing whitespace.
> hreitz Hanna Reitz
> warning: 1 line adds whitespace errors.
There is trailing whitespace after 'Reitz' that crept in.
>
> Anyhow,
> Tested-by: Philippe Mathieu-Daudé <philmd@oss.qualcomm.com>
>
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 :|
prev parent reply other threads:[~2026-06-24 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 12:29 [PATCH v2 0/2] Record maintainer/reviewer Git Lab handles Daniel P. Berrangé
2026-06-24 12:29 ` [PATCH v2 1/2] gitlab: introduce files mapping GitLab accounts to real names Daniel P. Berrangé
2026-06-24 13:09 ` Philippe Mathieu-Daudé
2026-06-24 13:11 ` Alex Bennée
2026-06-24 13:41 ` Fabiano Rosas
2026-06-24 16:43 ` Daniel P. Berrangé
2026-06-24 12:29 ` [PATCH v2 2/2] get_maintainer: add ability to report Git Lab handle Daniel P. Berrangé
2026-06-24 13:15 ` Alex Bennée
2026-06-24 13:19 ` [PATCH v2 0/2] Record maintainer/reviewer Git Lab handles Philippe Mathieu-Daudé
2026-06-24 17:38 ` Daniel P. Berrangé [this message]
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=ajwWMj0_3pht2uZM@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=farosas@suse.de \
--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.