wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Fredrik Strömberg" <stromberg@mullvad.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] WireGuard merged to net-next, on its way to Linux 5.6
Date: Mon, 9 Dec 2019 16:53:24 +0100	[thread overview]
Message-ID: <CANTUoed99k59kcEG0XUcsQMmFfixQm846_HDmsxQ0RN6otDf=Q@mail.gmail.com> (raw)
In-Reply-To: <87lfrlzf55.fsf@fifthhorseman.net>

On Mon, Dec 9, 2019 at 4:46 PM Daniel Kahn Gillmor
<dkg@fifthhorseman.net> wrote:
>
> 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...
>

I couldn't agree more. This is great news. Congratulations!
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09 10:12 [ANNOUNCE] WireGuard merged to net-next, on its way to Linux 5.6 Jason A. Donenfeld
2019-12-09 11:09 ` Laslo Hunhold
2019-12-09 15:34 ` Daniel Kahn Gillmor
2019-12-09 15:53   ` Fredrik Strömberg [this message]
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='CANTUoed99k59kcEG0XUcsQMmFfixQm846_HDmsxQ0RN6otDf=Q@mail.gmail.com' \
    --to=stromberg@mullvad.net \
    --cc=dkg@fifthhorseman.net \
    --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).