From: Martin Eskdale Moen <martinmoen@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Upstream Submission v1
Date: Thu, 2 Aug 2018 15:50:01 +0100 [thread overview]
Message-ID: <CAKiCHuO5Oe69bi4Lx8gYj85eaeJRHPD2jgcuCZUZse5E8R_zaA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pUYSU-D3rxF_V4B8Lhqfg_xb3Yj++MuBKZ6TK4epCBFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
Congrats Jason, I'm looking forward to seeing what they come up with but
also seeing Wireguard being in mainline.
On Tue, Jul 31, 2018 at 8:27 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> Hey list,
>
> I submitted patchset v1 of WireGuard to LKML a few minutes ago:
>
> [0/3] https://marc.info/?l=linux-netdev&m=153306429108040&w=2
> [1/3] https://marc.info/?l=linux-netdev&m=153306429908043&w=2
> [2/3] https://marc.info/?l=linux-netdev&m=153306437408074&w=2
> [3/3] https://marc.info/?l=linux-netdev&m=153306440208084&w=2
>
> I'm pretty elated, as getting v1 out the door marks a major milestone.
>
> I expect for the first submission to be mercilessly criticized from
> all sorts of interesting and useful angles. There will most certainly
> be a v2, and it will be better because of whatever intense criticism
> received from v1. So hold on tight: a wild process is about to begin.
>
> Regards,
> Jason
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #2: Type: text/html, Size: 2026 bytes --]
prev parent reply other threads:[~2018-08-02 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 19:26 Upstream Submission v1 Jason A. Donenfeld
2018-07-31 19:31 ` Joe Doss
2018-07-31 19:48 ` Reuben Martin
2018-07-31 21:13 ` Lee Yates
2018-07-31 22:28 ` Eric Light
2018-08-01 1:49 ` jugs
2018-08-01 4:40 ` Fredrik Strömberg
2018-08-02 13:42 ` Roman Mamedov
2018-08-02 14:50 ` Martin Eskdale Moen [this message]
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=CAKiCHuO5Oe69bi4Lx8gYj85eaeJRHPD2jgcuCZUZse5E8R_zaA@mail.gmail.com \
--to=martinmoen@gmail.com \
--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).