From: Pavel Roskin <proski@gnu.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Linux Wireless Summit -- Boston 2010
Date: Mon, 22 Feb 2010 16:57:28 -0500 [thread overview]
Message-ID: <1266875848.2594.42.camel@mj> (raw)
In-Reply-To: <20100222212029.GD2988@tuxdriver.com>
On Mon, 2010-02-22 at 16:20 -0500, John W. Linville wrote:
> Attendees will be required to register for LinuxCon 2010.
Why is it required? I could take one day off for the wireless summit,
but taking three or four days would be too much.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-02-22 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 13:57 Call For Proposal: Linux Wireless Summit(s) 2010 John W. Linville
2010-02-04 12:30 ` Johannes Berg
2010-02-05 16:31 ` John W. Linville
2010-02-22 21:20 ` Linux Wireless Summit -- Boston 2010 John W. Linville
2010-02-22 21:57 ` Pavel Roskin [this message]
2010-02-22 22:35 ` John W. Linville
2010-03-30 19:15 ` Cancelled/postponed -- " John W. Linville
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=1266875848.2594.42.camel@mj \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).