From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Cleber Rosa" <crosa@redhat.com>, "John Snow" <jsnow@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PULL 4/5] MAINTAINERS: update libvirt devel mailing list address
Date: Tue, 7 Nov 2023 21:16:35 +0100 [thread overview]
Message-ID: <ab47bd6d-4b85-4761-99e9-2c4b81023ff4@linaro.org> (raw)
In-Reply-To: <20231107190817.1607710-5-berrange@redhat.com>
On 7/11/23 20:08, Daniel P. Berrangé wrote:
> Effective immediately, the libvirt project has moved its list off
> libvir-list@redhat.com, to devel@lists.libvirt.org
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
FYI I already sent this one:
https://lore.kernel.org/qemu-devel/20231106110336.358-60-philmd@linaro.org/
I hope it gets merged smoothly.
Regards,
Phil.
next prev parent reply other threads:[~2023-11-07 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 19:08 [PULL 0/5] Misc fixes patches Daniel P. Berrangé
2023-11-07 19:08 ` [PULL 1/5] crypto/rsakey-builtin.c.inc: Clean up two error paths Daniel P. Berrangé
2023-11-07 19:08 ` [PULL 2/5] io: Stop appending -listen to net listeners Daniel P. Berrangé
2023-11-07 19:08 ` [PULL 3/5] audio: don't abort on f32 audio format in wav backend Daniel P. Berrangé
2023-11-07 19:08 ` [PULL 4/5] MAINTAINERS: update libvirt devel mailing list address Daniel P. Berrangé
2023-11-07 20:16 ` Philippe Mathieu-Daudé [this message]
2023-11-07 19:08 ` [PULL 5/5] scripts/cpu-x86-uarch-abi.py: Fix parameter error of cmd Daniel P. Berrangé
2023-11-08 14:20 ` [PULL 0/5] Misc fixes patches Stefan Hajnoczi
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=ab47bd6d-4b85-4761-99e9-2c4b81023ff4@linaro.org \
--to=philmd@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.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 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).