From: "Michael S. Tsirkin" <mst@redhat.com>
To: Mihai Carabas <mihai.carabas@oracle.com>
Cc: virtio-dev@lists.oasis-open.org, virt_wizards_us_grp@oracle.com
Subject: [virtio-dev] Re: Recommendations about VirtIo Spec Patch Submission
Date: Mon, 10 Jul 2017 17:27:04 +0300 [thread overview]
Message-ID: <20170710172253-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <3c1998ea-c802-8d82-64c4-de2db6fa05f4@oracle.com>
On Mon, Jul 10, 2017 at 04:07:39PM +0300, Mihai Carabas wrote:
> Hello Michael,
>
> My name is Mihai Carabas from Oracle Linux and Virtualization Engineering
> team. We currently are working on some VirtIo driver implementations. During
> the documentation part of the driver, we found some inconsistencies in
> various paragraphs of the VirtIo 1.0 Spec (all of them are about the
> form/terms used in the specification). What is the recommended way to submit
> patches with proposed modifications?
>
> Thank you,
> Mihai Carabas
>
> Oracle Linux and Virtualization Engineering
The most appropriate mailing list for spec comments is virtio-comment:
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=virtio#feedback
We are using git-svn to work with the repository:
https://tools.oasis-open.org/version-control/browse/wsvn/virtio/trunk/git-svn.txt
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2017-07-10 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3c1998ea-c802-8d82-64c4-de2db6fa05f4@oracle.com>
2017-07-10 13:40 ` [virtio-dev] Re: Recommendations about VirtIo Spec Patch Submission Mihai Carabas
2017-07-10 14:27 ` Michael S. Tsirkin [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=20170710172253-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=mihai.carabas@oracle.com \
--cc=virt_wizards_us_grp@oracle.com \
--cc=virtio-dev@lists.oasis-open.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