From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Gordon Bergling <gbe@freebsd.org>
Cc: Kyle Evans <kevans@freebsd.org>,
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: Wed, 17 Mar 2021 12:34:02 -0600 [thread overview]
Message-ID: <CAHmME9pqVfzWVsuTrC2eovbWTVeTSX086ZM6DSOK1ejPjkV3uQ@mail.gmail.com> (raw)
In-Reply-To: <YFH7yIJ9OImHUwYO@lion.0xfce3.net>
Hi Gordon,
On Wed, Mar 17, 2021 at 6:53 AM Gordon Bergling <gbe@freebsd.org> wrote:
> I am not sure, if the removal is a great idea, a removal from
> releng/13 and stable/13 - possibly yes, but from main?
>
> This is still -CURRENT and -CURRENT should be central place for development,
> even if we have phabricator for review.
It looks like Kyle has gone ahead with the revert anyway, so
development is now happening at:
https://git.zx2c4.com/wireguard-freebsd/
And there are now regular snapshot releases:
https://lists.zx2c4.com/pipermail/wireguard/2021-March/006518.html
As for your objections, and the question of what -CURRENT should or
shouldn't be used for, I really have no idea as a community outsider.
But I do look forward to submitting it for proper inclusion in
-CURRENT after a few more cycles of development and refinement.
There's also the crypto question that I'd welcome some feedback on:
https://lists.freebsd.org/pipermail/freebsd-hackers/2021-March/057076.html
> If the complete backout is happening, please don't forget the manual
> page. I have spend a lot of time on it, while OpenBSD made a good
> template.
Thanks for bringing this up; I had actually forgotten about that. Do
you want to re-add it and keep that current as we develop? If you
email me your SSH key, you can just commit it directly.
Jason
next prev parent reply other threads:[~2021-03-17 18:34 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 [this message]
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
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=CAHmME9pqVfzWVsuTrC2eovbWTVeTSX086ZM6DSOK1ejPjkV3uQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=freebsd-arch@freebsd.org \
--cc=freebsd-hackers@freebsd.org \
--cc=gbe@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).