From: Juan Quintela <quintela@redhat.com>
To: KVM devel mailing list <kvm@vger.kernel.org>,
qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: [Qemu-devel] KVM call minutes July 31th
Date: Tue, 31 Jul 2012 16:32:05 +0200 [thread overview]
Message-ID: <87haso6ly2.fsf@elfo.mitica> (raw)
Hi
Today minutes:
- Avi fixed and got 9p working
- QEMU 1.2 Test Day (stefan)
* Let's find -rc bugs and ensure the release is stable
* We've done this in the past and have a wiki template but can
discuss suggestions on the call
* A date?
- 1.2 plans for CPU model versioning/compatibility (eduardo)
(global properties vs QOM vs qdev)
how to do it ? configuration file? moving back to the code?
different external interface from internal one
Eduardo/Andreas/Anthony, <fill here>
next reply other threads:[~2012-07-31 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 14:32 Juan Quintela [this message]
2012-07-31 15:14 ` [Qemu-devel] QEMU CPU model versioning/compatibility (was Re: KVM call minutes July 31th) Eduardo Habkost
2012-08-01 8:50 ` Avi Kivity
2012-07-31 15:40 ` [Qemu-devel] KVM call minutes July 31th Eduardo Habkost
2012-07-31 15:56 ` Andreas Färber
2012-07-31 16:06 ` Igor Mammedov
2012-07-31 16:16 ` Andreas Färber
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=87haso6ly2.fsf@elfo.mitica \
--to=quintela@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).