virtio-comment

 View Only

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

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

    Posted 12-03-2019 05:43
    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>
    ---

    Changes from v1:
    - wording changes to address Cornelia's comments
    - move to near virtio-comment description

    README.md | 11 +++++++++++
    1 file changed, 11 insertions(+)

    diff --git a/README.md b/README.md
    index ffafb9b..2bdf485 100644
    --- a/README.md
    +++ b/README.md
    @@ -115,6 +115,17 @@ in HREF="https://github.com/oasis-tcs/virtio-admin">https://github.com/oasis-tcs/virtio-admin.


    +

    Implementation discussion


    +Implementation discussion should take place on the virtio-dev mailing list,
    +and be archived in the mailing list archives.
    +

    See +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

    +

    This is the correct list to copy on Linux virtio UAPI change proposals.
    +

    Note that only the 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.

    Use of github issues


    Note: according to the virtio TC rules, all official TC communication
    is taking place on one of the TC mailing lists.
    --
    MST