From: Lee Yates <rainmakerraw@icloud.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Upstream Submission v1
Date: Tue, 31 Jul 2018 21:13:42 +0000 [thread overview]
Message-ID: <emc0fe8fdc-bfd6-4d3a-a281-3dc302c9ee79@lee-pc> (raw)
In-Reply-To: <CAHmME9pUYSU-D3rxF_V4B8Lhqfg_xb3Yj++MuBKZ6TK4epCBFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Huge contrats, Jason et al.! A lot of work, but you got there *touch
wood*. This will open a lot of doors for the protocol, service providers
and end users.
- ------ Original Message ------
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Sent: 31/07/2018 20:26:53
Subject: Upstream Submission v1
>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
-----BEGIN PGP SIGNATURE-----
Version: BCPG C# v1.8.1.0
iQFBBAEBCAArBQJbYNEMJBxMZWUgWWF0ZXMgPHJhaW5tYWtlcnJhd0BpY2xvdWQu
Y29tPgAKCRDvJcvMOyipkpUbB/4pd9bTas2l+Ftk7MPPMl0hP0+QK1Ox3UGxJmWv
khWfrZDrrV7syobjN+2FEtA54ePAGKZpK6ic4n9dryTS3MM/A3dFPeZLoyLWFgWi
69ALg8EYNdCZRqqK57te4f8ldQh3J1exb0d/QmiVDSAWxsgIJ1fNL8UW0bilntDh
G26azO6MYDRA6Jj5ACS848mMeNa4Os2EttxOR2bJph1itRouitLNEm52spBZks6F
zk3KgATpThhliUwG4O5IAB3U4OU+mnqkjoGkW4ABq0hQyuUbld/v1AKrC+HgY+5J
I9ApGdd/SSN4dsqk1WCG/TbwdFR8u6m8q1PQ7Yz4ym/5X94L
=Df9j
-----END PGP SIGNATURE-----
[-- Attachment #2: rainmakerraw@icloud.com.asc --]
[-- Type: application/pgp-keys, Size: 1677 bytes --]
next prev parent reply other threads:[~2018-07-31 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 19:26 Jason A. Donenfeld
2018-07-31 19:31 ` Joe Doss
2018-07-31 19:48 ` Reuben Martin
2018-07-31 21:13 ` Lee Yates [this message]
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
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=emc0fe8fdc-bfd6-4d3a-a281-3dc302c9ee79@lee-pc \
--to=rainmakerraw@icloud.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).