From: Seth Forshee <seth.forshee@canonical.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Marcel Holtmann <marcel@holtmann.org>,
Larry Finger <Larry.Finger@lwfinger.net>,
Matt Chen <machen@suse.com>, joeyli <jlee@suse.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Linux summit this year ?
Date: Wed, 8 May 2013 08:20:30 -0500 [thread overview]
Message-ID: <20130508132030.GA32053@thinkpad-t410> (raw)
In-Reply-To: <20130507174445.GB2073@tuxdriver.com>
On Tue, May 07, 2013 at 01:44:45PM -0400, John W. Linville wrote:
> On Tue, May 07, 2013 at 11:42:36AM -0500, Seth Forshee wrote:
> > On Fri, May 03, 2013 at 10:49:47AM -0400, John W. Linville wrote:
> > > On Fri, May 03, 2013 at 10:11:10AM +0200, Johannes Berg wrote:
> > > > On Thu, 2013-05-02 at 15:43 -0400, John W. Linville wrote:
> > > >
> > > > > "I'm confirming that we got the space you needed for the Wireless Summit in
> > > > > New Orleans.
> > > >
> > > > > Does that sound alright to everyone?
> > > >
> > > > Sounds good to me. If it overlaps LPC, which one are people going to
> > > > have to register for (if not going to both anyway)?
> > >
> > > I would presume that if you want to got to LPC sessions then you
> > > would have to register for LPC. Generally we have required Wireless
> > > Summit attendees to register for LinuxCon, and I presume that would
> > > be required this time (so both LinuxCon and LPC if you want the
> > > LPC sessions).
> >
> > Why require LinuxCon registration rather than LPC? I'd assume most
> > wireless summit attendees are more interested in plumbers than LinuxCon.
> > Could the summit just require registration at one or the other?
>
> Well, I can ask. But the fact is that LPC and LCNA are separate
> events with separate events with separate budgets and expenses,
> separate organizers, etc.
>
> Anyway, I'll let you know what the event folks say...
It's not really a big deal for me, I just thought it a bit odd since the
audiences for wireless summit and LPC probably have more overlap. The
reasons you and Marcel gave make sense.
Thanks,
Seth
next prev parent reply other threads:[~2013-05-08 13:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALx5=V-wOkHb1Q4A_32LBQm9aP0dUL1J5s4ceLwqVGSYhfpwxw@mail.gmail.com>
2013-02-25 14:32 ` Linux summit this year ? John W. Linville
2013-02-25 16:29 ` Marcel Holtmann
2013-02-25 18:34 ` Larry Finger
2013-02-25 21:12 ` John W. Linville
2013-02-25 23:27 ` John W. Linville
2013-02-26 15:21 ` Marcel Holtmann
2013-05-02 19:27 ` Johannes Berg
2013-05-02 19:43 ` John W. Linville
2013-05-03 8:11 ` Johannes Berg
2013-05-03 14:49 ` John W. Linville
2013-05-03 14:52 ` Johannes Berg
2013-05-04 21:28 ` Arend van Spriel
2013-05-05 12:26 ` John W. Linville
2013-05-07 16:42 ` Seth Forshee
2013-05-07 17:44 ` John W. Linville
2013-05-08 13:20 ` Seth Forshee [this message]
2013-05-08 15:09 ` John W. Linville
[not found] ` <CALx5=V_4LOmZ=dkhtKmZ3FdgzEq6t4jSBogzoPn+KyFTBZ6Zvw@mail.gmail.com>
2013-05-13 14:07 ` John W. Linville
2013-05-07 18:30 ` Marcel Holtmann
2013-03-04 15:53 ` Johannes Berg
2013-05-22 17:18 ` Linux wireless summit, 19-20 September 2013 in New Orleans! 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=20130508132030.GA32053@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=Larry.Finger@lwfinger.net \
--cc=jlee@suse.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=machen@suse.com \
--cc=marcel@holtmann.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).