Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Cory Fields <lists@coryfields.com>
To: Bruno Wolff III <bruno@wolff.to>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard is now in Linus' tree
Date: Tue, 28 Jan 2020 20:46:49 -0500	[thread overview]
Message-ID: <CAApLimij+hsSCMmE+6367jnVkJ4mLYSmvpvq9U7Q4ncLXV-KUw@mail.gmail.com> (raw)
In-Reply-To: <20200129002159.GA9104@wolff.to>


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

Congratulations Jason, and everyone who has contributed.

I can't imagine how much work this took. Thank you for seeing it through!

Regards,
Cory Fields

On Tue, Jan 28, 2020, 7:40 PM Bruno Wolff III <bruno@wolff.to> wrote:

> Linus pulled in net-next about a half hour ago. So WireGuard is now
> officially upstream. Yeah!
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>

[-- Attachment #1.2: Type: text/html, Size: 1086 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:[~2020-01-29  1:47 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 [this message]
2020-01-29  8:43 ` Jason A. Donenfeld
2020-01-29  9:16   ` C Habs
2020-01-29  8:53 ` Laslo Hunhold
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=CAApLimij+hsSCMmE+6367jnVkJ4mLYSmvpvq9U7Q4ncLXV-KUw@mail.gmail.com \
    --to=lists@coryfields.com \
    --cc=bruno@wolff.to \
    --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).