qemu-rust.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	qemu-rust@nongnu.org
Subject: Re: qemu-rust@nongnu.org mailing list created
Date: Fri, 8 Nov 2024 19:10:17 +0000	[thread overview]
Message-ID: <CAAjaMXZ_VXE+2Wk-5EhdLARx2qS2qMuF7k6xRs21LdJ0vxPxXQ@mail.gmail.com> (raw)
In-Reply-To: <Zy4zXtZK_9OnXSJU@redhat.com>

On Fri, Nov 8, 2024 at 4:51 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> 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.


I will send a patch.


      reply	other threads:[~2024-11-08 22:05 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é
2024-11-08 19:10   ` Manos Pitsidianakis [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=CAAjaMXZ_VXE+2Wk-5EhdLARx2qS2qMuF7k6xRs21LdJ0vxPxXQ@mail.gmail.com \
    --to=manos.pitsidianakis@linaro.org \
    --cc=berrange@redhat.com \
    --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).