From: Roman Mamedov <rm@romanrm.net>
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 18:42:40 +0500 [thread overview]
Message-ID: <20180802184240.0e429391@natsu> (raw)
In-Reply-To: <CAHmME9pUYSU-D3rxF_V4B8Lhqfg_xb3Yj++MuBKZ6TK4epCBFg@mail.gmail.com>
On Tue, 31 Jul 2018 21:26:53 +0200
"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.
Congratulations, and a minor thing, please don't forget to CC: the WireGuard
mailing list on such submissions, so all subscribers here could take a peek on
replies to WG patches even if they don't follow the high-volume netdev list
themselves.
--
With respect,
Roman
next prev parent reply other threads:[~2018-08-02 13:32 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 [this message]
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=20180802184240.0e429391@natsu \
--to=rm@romanrm.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.