From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Juan Quintela <quintela@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 13:59:36 -0500 [thread overview]
Message-ID: <87wqqsjh0n.fsf@codemonkey.ws> (raw)
In-Reply-To: <20130521175357.GB6098@redhat.com>
"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Tue, May 21, 2013 at 09:29:07AM -0500, Anthony Liguori 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.
>
> I think you mean bi-weekly? If yes, ack.
I meant twice a month (or every other week).
Regards,
Anthony Liguori
>
>> >
>> >> 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?
>>
>> Regards,
>>
>> Anthony Liguori
>>
>> >
>> >> >
>> >> > Kevin - could you join on Tuesday? There appears a disconnect
>> >> > between the seabios and qemu that a conf call
>> >> > might help resolve.
>> >> >
>> >> > --
>> >> > MST
>> >> > --
>> >> > To unsubscribe from this list: send the line "unsubscribe kvm" in
>> >> > the body of a message to majordomo@vger.kernel.org
>> >> > More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-05-21 18:59 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
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 [this message]
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=87wqqsjh0n.fsf@codemonkey.ws \
--to=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=quintela@redhat.com \
--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