From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>,
"Fabiano Rosas" <farosas@suse.de>
Subject: Re: [PATCH v2 2/2] get_maintainer: add ability to report Git Lab handle
Date: Fri, 26 Jun 2026 11:06:09 +0100 [thread overview]
Message-ID: <aj5PEZkz-V6BEnmQ@redhat.com> (raw)
In-Reply-To: <87ik78krjq.fsf@draig.linaro.org>
On Wed, Jun 24, 2026 at 02:15:53PM +0100, Alex Bennée wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > With the GitLab mapping files from the previous commit, the
> > get_manitainer.pl script is now able to report the gitlab
> > handle for each maintainer/reviewer when displaying output.
> >
> > For example:
> >
> > $ ./scripts/get_maintainer.pl -f hw/scsi/lsi53c895a.c
> > Paolo Bonzini <pbonzini@redhat.com> (supporter:SCSI, gitlab:@bonzini)
> > Fam Zheng <fam@euphon.net> (reviewer:SCSI, gitlab:@famzheng)
> > qemu-devel@nongnu.org (open list:All patches CC here)
>
> I suspect it gets tripped up by utf-8 stuff:
>
> ➜ ./scripts/get_maintainer.pl -f contrib/gitdm/aliases
> "Alex Bennée" <alex.bennee@linaro.org> (odd fixer:GIT Data Mining C...)
> qemu-devel@nongnu.org (open list:All patches CC here)
>
> misses my tag.
The problem turned out to be that we failed to strip the double quotes
from the name before doing a lookup.
>
> However I think this approach is much cleaner. The other option would be
> embedding @refs in the M: line:
>
> M: Alex Bennée <alex.bennee@linaro.org> @stsquad
My previous version did
G: @stsquad
but it results in considerable duplication and made automated updates
harder. So based on Philippe's suggestion I split it into the map
files.
>
> and letting the script handle it. But I didn't want to hack on
> get_maintainer.pl which is why I started playing with a python version.
> However I need to add some features to it to reach usable parity with
> the perl script.
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-26 10:06 UTC|newest]
Thread overview: 11+ 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-26 10:06 ` Daniel P. Berrangé [this message]
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é
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=aj5PEZkz-V6BEnmQ@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.