From: Lars Kurth <lars.kurth@xen.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: anthony@codemonkey.ws,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Urgent, Input Needed] Moving the Xen Project Developer meeting to start a little earlier to accomodate for joint Xen-KVM Hackathon
Date: Tue, 10 Sep 2013 11:19:55 +0100 [thread overview]
Message-ID: <522EF24B.8070001@xen.org> (raw)
In-Reply-To: <1378802902.21748.18.camel@kazak.uk.xensource.com>
On 10/09/2013 09:48, Ian Campbell wrote:
> I think this is a reasonable thing to do, we should move it as early as
> we can, so out of 1000 and 1100 I would choose 1000. 0900-1200/1300 with
> no lunch included might be pushing it?
If we do it too early, the developer meeting is directly competing with
KVM Forum. We do have a few folks (e.g. from Intel, will likely want to
attend KVM forum as well as the Developer meeting). So I was looking for
a compromise.
Also, some people already booked their travel, arriving in the morning.
Which would potentially also be a problem, as they would miss the whole
dev meeting if we started too early.
So far, there was not an overwhelming response (just you). Unless, I get
more of a response for a joint Hackathon by TOMORROW, I am inclined to
assume you guys don't care and will put it on the back-burner.
Regards
Lars
next prev parent reply other threads:[~2013-09-10 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 17:29 [Urgent, Input Needed] Moving the Xen Project Developer meeting to start a little earlier to accomodate for joint Xen-KVM Hackathon Lars Kurth
2013-09-10 8:48 ` Ian Campbell
2013-09-10 10:19 ` Lars Kurth [this message]
2013-09-10 11:12 ` George Dunlap
2013-09-10 12:07 ` Lars Kurth
2013-09-10 14:32 ` Ian Campbell
2013-09-11 14:19 ` Lars Kurth
2013-09-10 10:19 ` Jan Beulich
2013-09-10 14:27 ` Stefano Stabellini
2013-09-13 3:33 ` Matt Wilson
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=522EF24B.8070001@xen.org \
--to=lars.kurth@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=anthony@codemonkey.ws \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).