From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Le Sandie <lesandie@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: October, Paris, France - Meticulous In-person WireGuard Codebase Study Session
Date: Wed, 11 Oct 2017 10:10:40 -0400 [thread overview]
Message-ID: <20171011141040.GA4586@gmail.com> (raw)
In-Reply-To: <CAKgwHq_V2N07F1ptfvtQMkVgbg+OYRJOFw57ZeRMehQFsmqcbQ@mail.gmail.com>
On Wed, Oct 11, 2017 at 03:52:14PM +0200, Le Sandie wrote:
>+1 for the live streaming and recording. I can attend virtually!
This should totally be a Twitch.tv session. :)
-K
next prev parent reply other threads:[~2017-10-11 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 23:19 Jason A. Donenfeld
2017-10-10 0:51 ` Ryan Whelan
2017-10-10 1:55 ` Eric Light
2017-10-10 5:06 ` Greg KH
2017-10-11 13:52 ` Le Sandie
2017-10-11 14:10 ` Konstantin Ryabitsev [this message]
2017-10-10 6:10 ` Greg KH
2017-10-10 6:36 ` Tom Bowditch
2017-10-13 11:14 ` Manuel Schölling
2017-10-22 9:55 ` Quentin
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=20171011141040.GA4586@gmail.com \
--to=konstantin@linuxfoundation.org \
--cc=lesandie@gmail.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).