OASIS Virtual I/O Device (VIRTIO) TC

 View Only

[PATCH] README.md: document use of virtio-dev

  • 1.  [PATCH] README.md: document use of virtio-dev

    Posted 12-02-2019 17:09
    People still seem to be confused which list is for what. Add a bit more text. Signed-off-by: Michael S. Tsirkin <mst@redhat.com> --- README.md 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index ffafb9b..1b72dc3 100644 --- a/README.md +++ b/README.md @@ -157,6 +157,17 @@ issue is resolved under the minor cleanups standing rule. and asking for a commit. </li> </ol> +<h4>Implementation discussion</h4> +Implementations should be discussed on the <strong>virtio-dev</strong> mailing list, +and are archived in the mailing list archives. +<p>See <A +HREF=" https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=virtio#feedback" ;> + https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=virtio#feedback </A> +<p>This is the correct list to copy on Linux virtio UAPI change proposals. +<p>Note that only plain text part of the message is archived, and all +attachments are stripped. Accordingly, messages sent to the +mailing list should use text/plain encoding and not +have any attachments. <h3>Contact</h3> <p>Please send questions or comments about <a href=" https://www.oasis-open.org/resources/tcadmin/github-repositories-for-oasis-tc-members-chartered-work" ;>OASIS TC GitHub repositories</a> to <a href=" mailto:robin@oasis-open.org" ;>Robin Cover</a> and <a href=" mailto:chet.ensign@oasis-open.org" ;>Chet Ensign</a>. For questions about content in this repository, please contact the TC Chair or Co-Chairs as listed on the the virtio TC's <a href=" https://www.oasis-open.org/committees/virtio/" ;>home page</a>.</p> </div> -- MST