From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call agenda for Mar 23
Date: Tue, 23 Mar 2010 11:52:29 +0200 [thread overview]
Message-ID: <4BA88F5D.6040008@redhat.com> (raw)
In-Reply-To: <4BA88A6F.2050703@web.de>
On 03/23/2010 11:31 AM, Jan Kiszka wrote:
> Chris Wright wrote:
>
>> Please send in any agenda items you are interested in covering.
>>
>> Yes, usability is a valid topic esp. if you promise to come w/ GUI patches.
>>
>>
> - state and roadmap for upstream merge of in-kernel device models
> (looks to me like this central merge effort is stalled ATM)
>
- alternative path of merging qemu-kvm.git's implementation as is and
cleaning it up in qemu.git.
For kvm.git, I wouldn't dream of merging something with outstanding
issues and cleaning them up "later", but the situation is somewhat
different with qemu vs qemu-kvm.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-03-23 9:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 6:11 KVM call agenda for Mar 23 Chris Wright
2010-03-23 8:40 ` Juan Quintela
2010-03-23 13:25 ` Juan Quintela
2010-03-23 9:31 ` Jan Kiszka
2010-03-23 9:52 ` Avi Kivity [this message]
2010-03-23 10:50 ` Jan Kiszka
2010-03-23 10:57 ` Avi Kivity
2010-03-23 11:13 ` Jan Kiszka
2010-03-23 12:29 ` Avi Kivity
2010-03-23 12:45 ` Anthony Liguori
2010-03-23 12:51 ` Avi Kivity
2010-03-23 12:56 ` [Qemu-devel] " Jes Sorensen
2010-03-25 1:31 ` Zhang, Xiantao
2010-03-25 9:39 ` Jan Kiszka
2010-03-25 9:43 ` Jes Sorensen
2010-03-26 18:48 ` Chris Wright
2010-03-23 12:40 ` Anthony Liguori
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=4BA88F5D.6040008@redhat.com \
--to=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=jan.kiszka@web.de \
--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