From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: Linux Wireless Summit -- 9-10 September 2010, San Francisco, CA, USA
Date: Thu, 19 Aug 2010 14:07:26 -0400 [thread overview]
Message-ID: <20100819180725.GD2672@tuxdriver.com> (raw)
As some of you are already aware, we will be having a Linux Wireless
Summit event in San Francisco in early September. More information
is available here:
http://wireless.kernel.org/en/developers/Summits/SanFranciscoBayArea-2010
Hopefully there will soon be information available regarding a reduced
hotel rate. When available, that information will be posted at the
link above -- be sure to subscribe to the Wiki updates! I believe
the reduced hotel rate will be $159/night and the reservations will
need to be made available before next Friday (27 August 2010), so
once the information is available do not delay!
If you plan to attend, please be sure to add your name to the Wiki
page at the URL above!
John
P.S. This event is sponsored by the Wi-Fi Alliance.
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
reply other threads:[~2010-08-19 18:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100819180725.GD2672@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.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).