From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Kyle Evans <kevans@freebsd.org>
Cc: freebsd-arch@freebsd.org,
FreeBSD Hackers <freebsd-hackers@freebsd.org>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Removing WireGuard Support From FreeBSD Base
Date: Thu, 18 Mar 2021 10:57:35 -0600 [thread overview]
Message-ID: <CAHmME9ombhO5+YHTJugxG0rZEGOFLh6zOw2CnG8OQNAywEHtSQ@mail.gmail.com> (raw)
In-Reply-To: <CACNAnaHit=-=rNy2DFZg6=zs1XFBvqt10Ta-MTM79NSWu1AK0w@mail.gmail.com>
Hi Kyle,
On Thu, Mar 18, 2021 at 10:53 AM Kyle Evans <kevans@freebsd.org> wrote:
> involved with this announcement that I'm leaving it for now. There's
> been too much press surrounding this, and it's distracting me from the
> work that I like to do and what I'm typically known for.
Makes sense and is understandable. It's been pretty miserable for all of us.
It looks like we'll eventually find somebody on the FreeBSD side of
things to take over where you left off, but hopefully for now in the
coming weeks things can just level out to some tranquility, so we can
get back to distraction-free coding without all the drama.
Jason
next prev parent reply other threads:[~2021-03-18 17:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 16:48 Kyle Evans
2021-03-16 17:13 ` Jeffrey Walton
2021-03-16 17:37 ` Jason A. Donenfeld
2021-03-16 18:24 ` Nicolai
2021-03-16 17:30 ` Jason A. Donenfeld
2021-03-17 12:53 ` Gordon Bergling
2021-03-17 18:34 ` Jason A. Donenfeld
2021-03-17 19:29 ` Wireguard for FreeBSD without iflib Frank Behrens
2021-03-17 22:17 ` Jason A. Donenfeld
2021-03-19 7:47 ` Removing WireGuard Support From FreeBSD Base Gordon Bergling
2021-03-19 10:43 ` Evilham
2021-03-18 16:52 ` Kyle Evans
2021-03-18 16:57 ` Jason A. Donenfeld [this message]
2021-03-18 18:49 John Jacobs
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=CAHmME9ombhO5+YHTJugxG0rZEGOFLh6zOw2CnG8OQNAywEHtSQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=freebsd-arch@freebsd.org \
--cc=freebsd-hackers@freebsd.org \
--cc=kevans@freebsd.org \
--cc=wireguard@lists.zx2c4.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 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).