From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>
Subject: Re: next wireless workshop - poll
Date: Wed, 18 May 2016 12:21:21 +0200 [thread overview]
Message-ID: <1463566881.2224.2.camel@sipsolutions.net> (raw)
In-Reply-To: <1461850005.2352.9.camel@sipsolutions.net> (sfid-20160428_152701_448618_8DAD4328)
On Thu, 2016-04-28 at 15:26 +0200, Johannes Berg wrote:
> Hi,
>
> Since I've been getting questions about the next possible workshop
> and
> its organisation, I decided to make a poll about it:
>
> http://goo.gl/forms/iMcE8b4TYU
>
> Please reply by
>
> May 16th
>
> so I can aggregate/evaluate the responses and we can make a decision.
>
I didn't get many responses, but only a single one preferring *only*
Tokyo, with a few others preferring Santa Fe.
So I'll look into the latter.
johannes
next prev parent reply other threads:[~2016-05-18 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 13:26 next wireless workshop - poll Johannes Berg
2016-05-18 10:21 ` Johannes Berg [this message]
2016-05-18 13:43 ` Jes Sorensen
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=1463566881.2224.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Jes.Sorensen@redhat.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 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.