On 2013年12月12日 01:32, Eric Blake wrote:
On 12/11/2013 01:49 AM, Stefan Hajnoczi wrote:
We are moving boldly on to QEMU 2.0 in the next release. Some patches
written at a time where we assumed 1.8 would be the next version number
managed to sneak in.
s/1.8/2.0/ in qapi-schema.json
Signed-off-b
On Wed, Dec 11, 2013 at 09:49:14AM +0100, Stefan Hajnoczi wrote:
> We are moving boldly on to QEMU 2.0 in the next release. Some patches
> written at a time where we assumed 1.8 would be the next version number
> managed to sneak in.
>
> s/1.8/2.0/ in qapi-schema.json
>
> Signed-off-by: Stefan H
On 12/11/2013 01:49 AM, Stefan Hajnoczi wrote:
> We are moving boldly on to QEMU 2.0 in the next release. Some patches
> written at a time where we assumed 1.8 would be the next version number
> managed to sneak in.
>
> s/1.8/2.0/ in qapi-schema.json
>
> Signed-off-by: Stefan Hajnoczi
> ---
>
On 2013年12月11日 16:49, Stefan Hajnoczi wrote:
We are moving boldly on to QEMU 2.0 in the next release. Some patches
written at a time where we assumed 1.8 would be the next version number
managed to sneak in.
s/1.8/2.0/ in qapi-schema.json
Signed-off-by: Stefan Hajnoczi
---
qapi-schema.json
We are moving boldly on to QEMU 2.0 in the next release. Some patches
written at a time where we assumed 1.8 would be the next version number
managed to sneak in.
s/1.8/2.0/ in qapi-schema.json
Signed-off-by: Stefan Hajnoczi
---
qapi-schema.json | 4 ++--
1 file changed, 2 insertions(+), 2 del