From: "John W. Linville" <linville@tuxdriver.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Linux wireless mini-summit -- Vancouver, Canada August 15-16, 2011
Date: Fri, 27 May 2011 09:07:01 -0400 [thread overview]
Message-ID: <20110527130701.GB28923@tuxdriver.com> (raw)
In-Reply-To: <BANLkTi=rTU=V_WXGsW2c4_ngrw5V7uVuwA@mail.gmail.com>
On Fri, May 27, 2011 at 11:44:00AM +0200, Helmut Schaa wrote:
> On Wed, May 4, 2011 at 9:47 PM, John W. Linville <linville@tuxdriver.com> wrote:
> > Attendees will be required to register for LinuxCon.
>
> Do you know if this is really necessary? I'll attend the wireless summit but not
> necessarily the LinuxCon afterwards.
Yes, it is necessary. LinuxCon is providing the facilities.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2011-05-27 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 19:47 Linux wireless mini-summit -- Vancouver, Canada August 15-16, 2011 John W. Linville
2011-05-04 23:58 ` wwguy
2011-05-27 9:44 ` Helmut Schaa
2011-05-27 13:07 ` John W. Linville [this message]
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=20110527130701.GB28923@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=helmut.schaa@googlemail.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).