From: Anthony Liguori <anthony@codemonkey.ws>
To: quintela@redhat.com
Cc: kvm-devel <kvm@vger.kernel.org>,
qemu-devel@nongnu.org, Jes Sorensen <Jes.Sorensen@redhat.com>,
"lmr@redhat.com" <lmr@redhat.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] KVM call agenda for April 05
Date: Mon, 04 Apr 2011 14:59:27 -0500 [thread overview]
Message-ID: <4D9A231F.6040004@codemonkey.ws> (raw)
In-Reply-To: <m38vvpom86.fsf@neno.mitica>
On 04/04/2011 02:22 PM, Juan Quintela wrote:
> Please, send in any agenda items you are interested in covering.
- KVM Forum -- do we have an ETA on CFP?
- Sub-maintainership -- how we can expand and improve upon it
- Trivial patch monkeys^Wteam -- this is an idea Stefan and I have been
kicking around to help some of the trivial patches get more attention on
the mailing list
- kvm-autotest -- I don't know if Lucas can join, but I'd like to get an
update on what the future plans around kvm-autotest is and also have a
discussion about what folks would like to see improved.
Regards,
Anthony Liguori
> Later, Juan.
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: quintela@redhat.com
Cc: "lmr@redhat.com" <lmr@redhat.com>,
Jes Sorensen <Jes.Sorensen@redhat.com>,
qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] KVM call agenda for April 05
Date: Mon, 04 Apr 2011 14:59:27 -0500 [thread overview]
Message-ID: <4D9A231F.6040004@codemonkey.ws> (raw)
In-Reply-To: <m38vvpom86.fsf@neno.mitica>
On 04/04/2011 02:22 PM, Juan Quintela wrote:
> Please, send in any agenda items you are interested in covering.
- KVM Forum -- do we have an ETA on CFP?
- Sub-maintainership -- how we can expand and improve upon it
- Trivial patch monkeys^Wteam -- this is an idea Stefan and I have been
kicking around to help some of the trivial patches get more attention on
the mailing list
- kvm-autotest -- I don't know if Lucas can join, but I'd like to get an
update on what the future plans around kvm-autotest is and also have a
discussion about what folks would like to see improved.
Regards,
Anthony Liguori
> Later, Juan.
>
>
next prev parent reply other threads:[~2011-04-04 19:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 19:22 KVM call agenda for April 05 Juan Quintela
2011-04-04 19:22 ` [Qemu-devel] " Juan Quintela
2011-04-04 19:59 ` Anthony Liguori [this message]
2011-04-04 19:59 ` Anthony Liguori
2011-04-04 20:38 ` Lucas Meneghel Rodrigues
2011-04-04 20:38 ` Lucas Meneghel Rodrigues
2011-04-05 6:01 ` Brad Hards
2011-04-05 8:27 ` Stefan Hajnoczi
2011-04-05 8:29 ` Alexander Graf
2011-04-05 8:42 ` Stefan Hajnoczi
2011-04-05 9:44 ` Brad Hards
2011-04-05 9:50 ` Alexander Graf
2011-04-05 10:53 ` Stefan Hajnoczi
2011-04-05 12:04 ` Brad Hards
2011-04-05 12:21 ` Brad Hards
2011-04-05 13:14 ` Stefan Hajnoczi
2011-04-05 20:25 ` Peter Maydell
2011-04-05 20:30 ` Anthony Liguori
2011-04-07 9:38 ` Harsh Bora
2011-04-05 9:36 ` Alon Levy
2011-04-05 9:36 ` Alon Levy
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=4D9A231F.6040004@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Jes.Sorensen@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.