From: Alex Williamson <alex.williamson@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Juan Quintela <quintela@redhat.com>,
Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call agenda for June 22
Date: Tue, 22 Jun 2010 07:21:28 -0600 [thread overview]
Message-ID: <1277212888.4669.335.camel@x201> (raw)
In-Reply-To: <4C20B14C.3040101@codemonkey.ws>
On Tue, 2010-06-22 at 07:49 -0500, Anthony Liguori wrote:
> On 06/22/2010 07:04 AM, Juan Quintela wrote:
> > 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.
> >
>
> Could we send the agenda note out a little bit earlier?
>
> The note arrived at 12:55am CST and we decided we had no agenda at
> 7:04am CST. That's a pretty short window and I imagine a lot of people
> in the US are not actually awake during that period of time :-)
Indeed, open at midnight, closed at 6am here. If anyone is still
interested, I'd like to talk about canonical device paths
(vmstate/ramblock naming).
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alex Williamson <alex.williamson@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] Re: KVM call agenda for June 22
Date: Tue, 22 Jun 2010 07:21:28 -0600 [thread overview]
Message-ID: <1277212888.4669.335.camel@x201> (raw)
In-Reply-To: <4C20B14C.3040101@codemonkey.ws>
On Tue, 2010-06-22 at 07:49 -0500, Anthony Liguori wrote:
> On 06/22/2010 07:04 AM, Juan Quintela wrote:
> > 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.
> >
>
> Could we send the agenda note out a little bit earlier?
>
> The note arrived at 12:55am CST and we decided we had no agenda at
> 7:04am CST. That's a pretty short window and I imagine a lot of people
> in the US are not actually awake during that period of time :-)
Indeed, open at midnight, closed at 6am here. If anyone is still
interested, I'd like to talk about canonical device paths
(vmstate/ramblock naming).
Alex
next prev parent reply other threads:[~2010-06-22 13:21 UTC|newest]
Thread overview: 18+ 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 5:55 ` [Qemu-devel] " Chris Wright
2010-06-22 12:04 ` Juan Quintela
2010-06-22 12:04 ` [Qemu-devel] " Juan Quintela
2010-06-22 12:49 ` Anthony Liguori
2010-06-22 12:49 ` [Qemu-devel] " Anthony Liguori
2010-06-22 13:21 ` Alex Williamson [this message]
2010-06-22 13:21 ` Alex Williamson
2010-06-22 13:23 ` Alexander Graf
2010-06-22 13:23 ` [Qemu-devel] " Alexander Graf
2010-06-22 13:33 ` Jes Sorensen
2010-06-22 13:33 ` Jes Sorensen
2010-06-22 14:10 ` Juan Quintela
2010-06-22 14:10 ` [Qemu-devel] " Juan Quintela
2010-06-22 14:40 ` Anthony Liguori
2010-06-22 14:40 ` [Qemu-devel] " Anthony Liguori
2010-06-22 14:52 ` Juan Quintela
2010-06-22 14:52 ` [Qemu-devel] " 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=1277212888.4669.335.camel@x201 \
--to=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=chrisw@redhat.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 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.