From: Till Kamppeter <till.kamppeter@gmail.com>
To: "'printing-summit@lists.linux-foundation.org'"
<printing-summit@lists.linux-foundation.org>,
Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: [Printing-architecture] Linux Foundation Summit Schedules are out
Date: Wed, 09 Mar 2011 00:06:46 +0100 [thread overview]
Message-ID: <4D76B686.5040600@gmail.com> (raw)
Hi,
here are the schedules of the LF Summit:
http://events.linuxfoundation.org/events/collaboration-summit/schedule
The LSB meeting is during the whole Friday, no other days. There is no
desktop-oriented meeting at all and also no Driver Backports meeting.
MeeGo is on Thursday and on Friday AM.
This means that we have to schedule the joint meeting with LSB on
Friday, as usual in our room due to the call-in service.
Perhaps we could also arrange a joint meeting with MeeGo as part of our
mobile session. WDYT?
For the OpenPrinting Summit we have the Kyoto room on all three days.
Till
next reply other threads:[~2011-03-08 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 23:06 Till Kamppeter [this message]
2011-03-08 23:29 ` [Printing-architecture] [Printing-summit] Linux Foundation Summit Schedules are out Petrie, Glen
2011-03-17 13:47 ` Till Kamppeter
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=4D76B686.5040600@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=printing-summit@lists.linux-foundation.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 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.