Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] WireGuard merged to net-next, on its way to Linux 5.6
Date: Mon, 09 Dec 2019 10:34:46 -0500	[thread overview]
Message-ID: <87lfrlzf55.fsf@fifthhorseman.net> (raw)
In-Reply-To: <CAHmME9oRJqvMWF9rnSZejWe9J6ONUMbk108VkH1Qfy513Vp=dg@mail.gmail.com>


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

On Mon 2019-12-09 11:12:23 +0100, Jason A. Donenfeld wrote:
> 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.

Congratulations!  This is excellent news.

I know the path to this process is a long and winding one, and involves
lots of changes and compromises.  but i am really glad that this project
has stuck through it all.  The additional reach for the project (both in
terms of users and in terms of developer eyeballs) is huge.

Looking forward to thinking through what possibilities open up next
here...

    --dkg

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

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

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

  parent reply	other threads:[~2019-12-09 15:41 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
2019-12-09 15:34 ` Daniel Kahn Gillmor [this message]
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=87lfrlzf55.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=Jason@zx2c4.com \
    --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).