From: Luiz Capitulino <lcapitulino@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] Re: KVM call agenda for Feb 1
Date: Tue, 1 Feb 2011 10:56:55 -0200 [thread overview]
Message-ID: <20110201105655.2ed0bcf6@doriath> (raw)
In-Reply-To: <20110201105321.0d2901b6@doriath>
On Tue, 1 Feb 2011 10:53:21 -0200
Luiz Capitulino <lcapitulino@redhat.com> wrote:
> On Mon, 31 Jan 2011 15:39:22 -0600
> Anthony Liguori <anthony@codemonkey.ws> wrote:
>
> > On 01/31/2011 12:10 PM, Jan Kiszka wrote:
> > > On 2011-01-31 11:02, Juan Quintela wrote:
> > >
> > >> Please send in any agenda items you are interested incovering.
> > >>
> > >>
> > > o KVM upstream merge: status, plans, coordination
> > >
> >
> > o QMP support status for 0.14. Luiz and I already chatted about it
> > today but would be good to discuss in the call just to see if anyone has
> > opinions. Basically, declare it fully supported with a few minor
> > caveats (like human-monitor-passthrough is no more supported than the
> > actual monitor and recommendations about how to deal with devices in the
> > device tree).
>
> o Summer of code 2011
Forgot to mention the wiki page:
http://wiki.qemu.org/Google_Summer_of_Code_2011
next prev parent reply other threads:[~2011-02-01 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 10:02 [Qemu-devel] KVM call agenda for Feb 1 Juan Quintela
2011-01-31 18:10 ` [Qemu-devel] " Jan Kiszka
2011-01-31 21:39 ` Anthony Liguori
2011-02-01 12:40 ` Paolo Bonzini
2011-02-01 12:53 ` Luiz Capitulino
2011-02-01 12:56 ` Luiz Capitulino [this message]
2011-02-01 14:37 ` Alexander Graf
2011-02-01 15:05 ` Anthony Liguori
2011-02-01 15:27 ` Alexander Graf
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=20110201105655.2ed0bcf6@doriath \
--to=lcapitulino@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).