From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Manos Pitsidianakis <manos.pitsidianakis@linaro.org>,
qemu-rust@nongnu.org
Subject: Re: qemu-rust@nongnu.org mailing list created
Date: Fri, 8 Nov 2024 15:50:54 +0000 [thread overview]
Message-ID: <Zy4zXtZK_9OnXSJU@redhat.com> (raw)
In-Reply-To: <CAFEAcA-ZQuyGTtG-vhRTEwpz0L4cpimNxkKix45Yw6gVHXozRQ@mail.gmail.com>
On Fri, Nov 08, 2024 at 03:13:58PM +0000, Peter Maydell wrote:
> One of the things suggested at the KVM Forum Rust BoF was creating
> a qemu-rust mailing list. This is going to be one of our usual
> qemu-foo lists along the lines of what we have already for
> qemu-block, qemu-arm, etc, and the standard policy applies: emails
> to qemu-rust should also cc qemu-devel so people subscribed to
> qemu-devel only can see traffic. The separate list will hopefully
> assist people who want to follow Rust-related discussion and patches
> in identifying those emails.
>
> You can subscribe here if you like:
> https://lists.nongnu.org/mailman/listinfo/qemu-rust
>
> The list should be set up with basically the same config as qemu-devel;
> in particular it accepts posts from non-members (though there might be
> a slight delay on first posting from a non-member).
>
> Please cc qemu-rust on future Rust related discussions and any
> patches that touch or add Rust code.
Can we get qemu-rust@nongnu.org added to the MAINTAINERS file
for every entry which touches the rust/ subtree.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-11-08 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 15:13 qemu-rust@nongnu.org mailing list created Peter Maydell
2024-11-08 15:50 ` Daniel P. Berrangé [this message]
2024-11-08 19:10 ` Manos Pitsidianakis
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=Zy4zXtZK_9OnXSJU@redhat.com \
--to=berrange@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@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).