From: Stephen Hemminger <stephen@networkplumber.org>
To: Hajime Tazaki <thehajime@gmail.com>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
linux-wireless@vger.kernel.org, lwn@lwn.net
Subject: Re: [ANNOUNCE] Netdev 1.2 conference
Date: Mon, 16 May 2016 11:50:08 -0700 [thread overview]
Message-ID: <20160516115008.0dc2c795@xeon-e3> (raw)
In-Reply-To: <m2shxi10bp.wl@gmail.com>
On Tue, 17 May 2016 00:36:58 +0900
Hajime Tazaki <thehajime@gmail.com> wrote:
> Following the last successful Netdev 0.1 in Ottawa, Canada and
> 1.1 in Seville, Spain. We are happy to announce the third Netdev conference:
> Netdev 1.2 (year 1, conference 2) from 5th to 7th October 2016 in Tokyo,
> Japan (http://netdevconf.org/1.2/).
I understand that getting a free date for a conference is hard to find,
but those dates overlap with LinuxCon Europe in Berlin. There may not
be a lot of overlap in possible attendees but it seems like there might
be a better date?
next prev parent reply other threads:[~2016-05-16 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 15:36 [ANNOUNCE] Netdev 1.2 conference Hajime Tazaki
2016-05-16 18:50 ` Stephen Hemminger [this message]
2016-05-17 15:28 ` Hajime Tazaki
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=20160516115008.0dc2c795@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=thehajime@gmail.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 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.