From: Stefano Garzarella <sgarzare@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio-comment@lists.linux.dev, virtio-dev@lists.linux.dev
Subject: Re: [PATCH v3] README.md: update mailing list info
Date: Thu, 16 May 2024 10:15:54 +0200 [thread overview]
Message-ID: <te6tzbegqky7uz4skrag3yowet3phtq6nn7tegyrillgb4juwn@m4gi5ohfuk7m> (raw)
In-Reply-To: <8f5db33c96d685fcebca3579b05d09b64dd720d9.1715766697.git.mst@redhat.com>
On Wed, May 15, 2024 at 05:53:14AM GMT, Michael S. Tsirkin wrote:
>As approved by the TC, we are moving to a less formal
>way of discussing the specification, on the mailing lists
>provided by the Linux Foundation:
>
>https://groups.oasis-open.org/higherlogic/ws/public/ballot?id=3820
>
>Update README.md, CONTRIBUTING.md and newdevice.tex accordingly.
>
>Use this opportunity to explain when and how to use each
>mailing list.
>
>Oh yes, and device numbers are reserved through virtio-comment
>not through virtio-dev. Correct that.
>
>Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>---
>
>changes from v3:
> update CONTRIBUTING.md and newdevice.tex
>changes from v2:
> Use this opportunity to explain when and how to use each mailing list.
>
> CONTRIBUTING.md | 2 +-
> README.md | 80 ++++++++++++++++++++++++++++++++++++++++++-------
> newdevice.tex | 3 +-
> 3 files changed, 72 insertions(+), 13 deletions(-)
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
prev parent reply other threads:[~2024-05-16 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 9:53 [PATCH v3] README.md: update mailing list info Michael S. Tsirkin
[not found] ` <PH0PR12MB54818B506EFE9E4ED61B4294DCEC2@PH0PR12MB5481.namprd12.prod.outlook.com>
2024-05-15 10:30 ` Michael S. Tsirkin
[not found] ` <PH0PR12MB54818853B8A407B6F2A3D463DCEC2@PH0PR12MB5481.namprd12.prod.outlook.com>
2024-05-15 10:37 ` Michael S. Tsirkin
2024-05-16 8:15 ` Stefano Garzarella [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=te6tzbegqky7uz4skrag3yowet3phtq6nn7tegyrillgb4juwn@m4gi5ohfuk7m \
--to=sgarzare@redhat.com \
--cc=mst@redhat.com \
--cc=virtio-comment@lists.linux.dev \
--cc=virtio-dev@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).