On Mon, Aug 19, 2013 at 12:45:21PM +0930, Rusty Russell wrote:
> "Michael S. Tsirkin" <> writes:
> > I think it's useful to formalize the proposal for
> > the new config layout and how interoperability is
> > handled.
> >
> > A Linux driver written by Rusty and qemu side by me
> > have both been published.
> >
> > It shouldn't be hard to put this in the spec form - Rusty,
> > do you plan to do it or should I take a stub at it?
>
> I'd love you to do it. In fact, I already assigned it to you :)
>
> https://tools.oasis-open.org/issues/browse/VIRTIO-21
>
> Here's the process I've imagined:
>
> 1) Create / Assign issue if there isn't one:
> https://tools.oasis-open.org/issues/browse/VIRTIO
>
> 2) Post patch to mailing list.
>
> 3) Once there's agreement and you want the patch applied, mark the
> issue OPEN with the URL of final patch (eg. mailing list URL).
>
> 4) Next meeting we go through OPEN and decide what we can apply, what
> needs deferring, etc.
Okay.
So ... which version should the patch apply to?
> Cheers,
> Rusty.
> PS. If other people want to take over jobs on that list, please do!
>
>
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe:
> Unsubscribe:
> List help:
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/
