From: Juan Quintela <quintela@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
KVM devel mailing list <kvm@vger.kernel.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
kevin@koconnor.net, seabios@seabios.org, ddutile@redhat.com
Subject: Re: KVM call agenda for 2013-05-21
Date: Tue, 21 May 2013 16:34:14 +0200 [thread overview]
Message-ID: <87txlwqu55.fsf@elfo.elfo> (raw)
In-Reply-To: <87d2skz9sc.fsf@codemonkey.ws> (Anthony Liguori's message of "Tue, 21 May 2013 09:29:07 -0500")
Anthony Liguori <anthony@codemonkey.ws> wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
>
>> On Tue, May 21, 2013 at 07:18:58AM -0500, Anthony Liguori wrote:
>>> "Michael S. Tsirkin" <mst@redhat.com> writes:
>>>
>>> > On Mon, May 20, 2013 at 12:57:47PM +0200, Juan Quintela wrote:
>>> >>
>>> >> Hi
>>> >>
>>> >> Please, send any topic that you are interested in covering.
>>> >>
>>> >> Thanks, Juan.
>>> >
>>> > Generating acpi tables.
>>> >
>>> > Cc'd a bunch of people who might be interested in this topic.
>>>
>>> Unfortunately I have a conflict this morning so I won't be able to
>>> join. I just saw Kevin's response here from last week and I'll respond
>>> to it later this morning.
>>
>> Unfortunate.
>> Let's talk about this on the next slot: next Tuesday, June 4 then.
>> Could you keep your agenda clear on that day please?
>
> Ack.
>
> Perhaps we could move this call to bimonthly and cancel it less
> frequently? That will make it easier to reserve calendar time for it.
bimonthly or bi-weekly?
About sending the call on Friday/Thrusday, I can change.
>
>>
>>> Can we post the call for agenda for this call on Fridays in the future?
>>> I need more than 24 hours to make sure to keep my calendar clear...
>>>
>>> Regards,
>>>
>>> Anthony Liguori
>>
>> We don't work on Fridays in Israel so that means we'll only be able to
>> respond Sunday, and you'll only see it Monday anyway.
>> Setting agenda Thursday is probably too aggressive?
>
> Maybe we could use a wiki page to setup a rolling agenda?
I think this could be easier for everybody involved.
Especially because you just look if there is anything to discuss?
Later, Juan.
next prev parent reply other threads:[~2013-05-21 14:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 10:57 KVM call agenda for 2013-05-21 Juan Quintela
2013-05-20 13:25 ` Michael S. Tsirkin
2013-05-21 12:18 ` Anthony Liguori
2013-05-21 12:33 ` Michael S. Tsirkin
2013-05-21 14:29 ` Anthony Liguori
2013-05-21 14:34 ` Juan Quintela [this message]
2013-05-21 16:40 ` [Qemu-devel] " Andreas Färber
2013-05-21 17:52 ` Michael S. Tsirkin
2013-05-21 17:53 ` Michael S. Tsirkin
2013-05-21 18:59 ` Anthony Liguori
2013-05-21 14:00 ` 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=87txlwqu55.fsf@elfo.elfo \
--to=quintela@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=ddutile@redhat.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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