From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [virtio] Re: [PATCH v2 0/2] two versioning related changes
Date: Tue, 13 Feb 2018 17:27:39 +0100 [thread overview]
Message-ID: <20180213172739.6ffa3735.cohuck@redhat.com> (raw)
In-Reply-To: <1518525848-8307-1-git-send-email-pasic@linux.vnet.ibm.com>
On Tue, 13 Feb 2018 13:44:06 +0100
Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
> v1->v2:
> * fixed ungrammatical commit title for #1
> * added r-b's
> * added bug tracker references
>
> Halil Pasic (2):
> ccw: be more precise about the semantic of revision 1
> introduction: simplify the designation of legacy
>
> content.tex | 2 +-
> introduction.tex | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
Changes look fine to me.
Some minor nits for the issues:
- I think the reported versions should only refer to released versions
(and not to the review versions?)
- Please add a "Proposed patch" reference in the Proposal: field.
Otherwise, I think this is ready for voting.
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
next prev parent reply other threads:[~2018-02-13 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 12:44 [virtio] [PATCH v2 0/2] two versioning related changes Halil Pasic
2018-02-13 12:44 ` [virtio] [PATCH v2 1/2] ccw: be more precise about the semantic of revision 1 Halil Pasic
2018-02-13 12:44 ` [virtio] [PATCH v2 2/2] introduction: simplify the designation of legacy Halil Pasic
2018-02-13 14:41 ` [virtio] Re: [PATCH v2 0/2] two versioning related changes Michael S. Tsirkin
2018-02-13 16:27 ` Cornelia Huck [this message]
2018-02-28 15:56 ` Cornelia Huck
2018-02-28 16:25 ` Halil Pasic
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=20180213172739.6ffa3735.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtio@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