From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Subject: Statement regarding NetDev conference and NetDev Society
Date: Sat, 17 Mar 2018 16:25:22 -0400 (EDT) [thread overview]
Message-ID: <20180317.162522.1694397764386221487.davem@davemloft.net> (raw)
As the Linux networking maintainer, I would like to make clear my
relationship with the Netdev Society and its event, the NetDev
conference. I am no longer associated with either.
I am writing to provide clarity on this situation to the subscribers
of the 'netdev' mailing list and the community at large.
Specifically, I am writing to make sure there isn't any confusion
through the use of the name "NetDev" that I either continue to plan,
support or participate in this event. I do not.
While in the past I have participated in the NetDev events as a member of
the NetDev technical committee and as a member of the NetDev Society's
board, I have formally left the board, am no longer associated with
planning the NetDev conference and do not intend to participate in future
NetDev conference events.
Having said all of this, I look forward to continued great work on the
netdev project and sharing cool advances in networking at the networking
track of Linux Plumbers Conference.
reply other threads:[~2018-03-17 20:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180317.162522.1694397764386221487.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@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).