From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@mailo.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Warner Losh" <imp@bsdimp.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Kyle Evans" <kevans@freebsd.org>,
"Li-Wen Hsu" <lwhsu@freebsd.org>,
"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>
Subject: [PULL 0/5] Misc patches
Date: Tue, 21 Jul 2026 16:55:49 +0100 [thread overview]
Message-ID: <20260721155554.128840-1-berrange@redhat.com> (raw)
The following changes since commit bd6079a7a1d14de0918a7715ef6db85dc32de3bb:
Merge tag 'next-pull-request' of https://gitlab.com/peterx/qemu into staging (2026-07-20 11:12:38 -0400)
are available in the Git repository at:
https://gitlab.com/berrange/qemu tags/misc-next-pull-request
for you to fetch changes up to 84a6c5f94b3d3c445c55189d38aca22234054c10:
get_maintainer: add ability to report Git Lab handle (2026-07-21 16:53:12 +0100)
----------------------------------------------------------------
* Update FreeBSD image to 14.4
* Fix inotify test for FreeBSD 15
* Fix crypt/nettle build option argument handling
* Add tracking & reporting of GitLab account handles for maintainers
----------------------------------------------------------------
Daniel P. Berrangé (3):
tests/vm: update to FreeBSD 14.4 image
gitlab: introduce files mapping GitLab accounts to real names
get_maintainer: add ability to report Git Lab handle
Jessica Clarke (1):
test-util-filemonitor: Adapt to FreeBSD 15's native inotify semantics
Luc Michel (1):
meson.build: re-add explicit gcrypt/nettle request check
.gitlab-map-auto | 93 ++++++++++++++++++++++++++++++
.gitlab-map-manual | 18 ++++++
crypto/cipher.c | 2 +-
crypto/meson.build | 2 +-
meson.build | 11 +++-
scripts/get_maintainer.pl | 53 +++++++++++++++--
scripts/gitlab-map-check | 51 ++++++++++++++++
scripts/gitlab-map-update | 45 +++++++++++++++
tests/unit/test-crypto-block.c | 3 +-
tests/unit/test-util-filemonitor.c | 29 +++++++++-
tests/vm/freebsd | 4 +-
11 files changed, 300 insertions(+), 11 deletions(-)
create mode 100644 .gitlab-map-auto
create mode 100644 .gitlab-map-manual
create mode 100755 scripts/gitlab-map-check
create mode 100755 scripts/gitlab-map-update
--
2.55.0
next reply other threads:[~2026-07-21 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 15:55 Daniel P. Berrangé [this message]
2026-07-21 15:55 ` [PULL 1/5] test-util-filemonitor: Adapt to FreeBSD 15's native inotify semantics Daniel P. Berrangé
2026-07-21 15:55 ` [PULL 2/5] tests/vm: update to FreeBSD 14.4 image Daniel P. Berrangé
2026-07-21 15:55 ` [PULL 3/5] meson.build: re-add explicit gcrypt/nettle request check Daniel P. Berrangé
2026-07-21 15:55 ` [PULL 4/5] gitlab: introduce files mapping GitLab accounts to real names Daniel P. Berrangé
2026-07-21 15:55 ` [PULL 5/5] get_maintainer: add ability to report Git Lab handle Daniel P. Berrangé
-- strict thread matches above, loose matches on Subject: below --
2021-09-14 13:01 [PULL 0/5] Misc patches marcandre.lureau
2021-09-14 19:10 ` Peter Maydell
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=20260721155554.128840-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=lwhsu@freebsd.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@mailo.com \
--cc=pierrick.bouvier@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.