All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org,
	Cornelia Huck <cohuck@redhat.com>
Subject: [virtio] Re: [PATCH 0/2] two versioning related changes
Date: Fri, 9 Feb 2018 22:43:23 +0200	[thread overview]
Message-ID: <20180209220411-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1518206354-29610-1-git-send-email-pasic@linux.vnet.ibm.com>

On Fri, Feb 09, 2018 at 08:59:12PM +0100, Halil Pasic wrote:
> Regarding patch #1 please see also:
> https://lists.oasis-open.org/archives/virtio/201802/msg00018.html

Fine by me. Can you please open an issue to track it?
This makes it easier for me to start voting.

If you would rather use github issues,
that'd be great. There seem to be easy tools
to work with their API, e.g.
http://search.cpan.org/~fayland/Net-GitHub-0.93/lib/Net/GitHub/V3/Issues.pm

We need to come up with a schema to keep the following info in github:
- what is the issue title/short description
- which version fixes the issue?
- what is the proposed spec change?

and then send a script that can get an issue # and
print that, similar to virtio-jira.pl in virtio-admin.

Help with that is very welcome but if you'd rather not you
can just use jira for now.
Pls remember to set fixed in to 1.1 and environment to
reporter name and email (yourself).


> Halil Pasic (2):
>   ccw: be more precise the semantic of revision 1
>   introduction: simplify the designation of legacy
> 
>  content.tex      |    2 +-
>  introduction.tex |    4 ++--
>  2 files changed, 3 insertions(+), 3 deletions(-)

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


  parent reply	other threads:[~2018-02-09 20:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 19:59 [virtio] [PATCH 0/2] two versioning related changes Halil Pasic
2018-02-09 19:59 ` [virtio] [PATCH 1/2] ccw: be more precise the semantic of revision 1 Halil Pasic
2018-02-12 12:59   ` [virtio] " Cornelia Huck
2018-02-12 14:25     ` [virtio] Re: [virtio-dev] " Halil Pasic
2018-02-12 21:09       ` Michael S. Tsirkin
2018-02-12 22:47         ` Halil Pasic
2018-02-09 19:59 ` [virtio] [PATCH 2/2] introduction: simplify the designation of legacy Halil Pasic
2018-02-12 13:00   ` [virtio] " Cornelia Huck
2018-02-09 20:43 ` Michael S. Tsirkin [this message]
2018-02-12 13:03   ` [virtio] Re: [PATCH 0/2] two versioning related changes Cornelia Huck
2018-02-12 14:29     ` 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=20180209220411-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.