From: Juan Quintela <quintela@redhat.com>
To: Chris Wright <chrisw@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call agenda for June 22
Date: Tue, 22 Jun 2010 14:04:44 +0200 [thread overview]
Message-ID: <m3hbkvff37.fsf@trasno.mitica> (raw)
In-Reply-To: <20100622055542.GA4104@x200.localdomain> (Chris Wright's message of "Mon, 21 Jun 2010 22:55:42 -0700")
Chris Wright <chrisw@redhat.com> wrote:
> Please send in any agenda items you are interested in covering.
>
> If we have a lack of agenda items I'll cancel the week's call.
As we have no agenda. This week call gets cancelled.
Thanks, Juan.
> thanks,
> -chris
next prev parent reply other threads:[~2010-06-22 12:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 5:55 KVM call agenda for June 22 Chris Wright
2010-06-22 12:04 ` Juan Quintela [this message]
2010-06-22 12:49 ` Anthony Liguori
2010-06-22 13:21 ` Alex Williamson
2010-06-22 13:23 ` Alexander Graf
2010-06-22 13:33 ` [Qemu-devel] " Jes Sorensen
2010-06-22 14:10 ` Juan Quintela
2010-06-22 14:40 ` Anthony Liguori
2010-06-22 14:52 ` Juan Quintela
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=m3hbkvff37.fsf@trasno.mitica \
--to=quintela@redhat.com \
--cc=chrisw@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