From: Laslo Hunhold <dev@frign.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Wireguard is now in Linus' tree
Date: Wed, 29 Jan 2020 09:53:59 +0100 [thread overview]
Message-ID: <20200129095359.2fd5da35@frign.de> (raw)
In-Reply-To: <20200129002159.GA9104@wolff.to>
On Tue, 28 Jan 2020 18:21:59 -0600
Bruno Wolff III <bruno@wolff.to> wrote:
Dear Bruno,
> Linus pulled in net-next about a half hour ago. So WireGuard is now
> officially upstream. Yeah!
This is great news! Thanks to all contributors and supporters for the
endurance to pull this through! There is a bright future ahead of us.
With best regards
Laslo Hunhold
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-01-30 2:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 0:21 Bruno Wolff III
2020-01-29 0:39 ` Paul Hedderly
2020-01-29 1:46 ` Cory Fields
2020-01-29 8:43 ` Jason A. Donenfeld
2020-01-29 9:16 ` C Habs
2020-01-29 8:53 ` Laslo Hunhold [this message]
2020-01-30 17:31 ` Germano Massullo
2020-01-30 17:44 ` Erik Carlin
2020-01-30 21:22 ` Jakub Juraszek
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=20200129095359.2fd5da35@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).