Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Laslo Hunhold <dev@frign.de>
To: wireguard@lists.zx2c4.com
Subject: Re: [ANNOUNCE] WireGuard merged to net-next, on its way to Linux 5.6
Date: Mon, 9 Dec 2019 12:09:55 +0100	[thread overview]
Message-ID: <20191209120955.46b715c0@frign.de> (raw)
In-Reply-To: <CAHmME9oRJqvMWF9rnSZejWe9J6ONUMbk108VkH1Qfy513Vp=dg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 873 bytes --]

On Mon, 9 Dec 2019 11:12:23 +0100
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:

Dear Jason,

> I'm happy to announce that WireGuard has been merged into Dave
> Miller's net-next tree. That means when Linus Torvalds opens up his
> tree for Linux 5.6, Dave will send a pull request to Linus, and
> WireGuard will wind up in Linux 5.6.
> 
> This is big news and very exciting.
> 
> Thanks to all the developers, contributors, users, advisers, and
> mailing list interlocutors who have helped to make this happen.
> 
> In the coming hours and days I'll be sending followups on next steps.

this is great news! Maintaining a patchset out of tree is always a big
burden, so seeing it in-tree (despite some compromises) is a good
thing and will help focus more on other aspects in the userspace. Keep
up the great work!

With best regards

Laslo Hunhold

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2019-12-09 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09 10:12 Jason A. Donenfeld
2019-12-09 11:09 ` Laslo Hunhold [this message]
2019-12-09 15:34 ` Daniel Kahn Gillmor
2019-12-09 15:53   ` Fredrik Strömberg
2019-12-10 15:31     ` jugs

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=20191209120955.46b715c0@frign.de \
    --to=dev@frign.de \
    --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).