All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: October, Paris, France - Meticulous In-person WireGuard Codebase Study Session
Date: Tue, 10 Oct 2017 08:10:54 +0200	[thread overview]
Message-ID: <20171010061054.GA7113@kroah.com> (raw)
In-Reply-To: <CAHmME9ovdYWEMkQKedvO+-4p4X5dOVARFhQ_W74sXJyvP=53Pg@mail.gmail.com>

On Tue, Oct 10, 2017 at 01:19:45AM +0200, Jason A. Donenfeld wrote:
> Hey folks,
> 
> A few friends asked if I'd do a meticulous read through and
> explanation, in person, of every line of the relatively short
> WireGuard code base. We had done this at some point in 2015, before
> the project was made public, and it took several highly intense hours
> to study the whole thing, but was a fairly interesting time for all
> (though undoubtedly mentally exhausting to the fullest).
> 
> Now they're asking me to do it again. But this time I thought I'd
> extend the session to a bit larger group.
> 
> If anybody is in Paris during the next few weeks and would like to
> attend, please let me know, either on list or off list, and we'll pick
> a time and place and all meet up for several hours of intense study.

Count me in, should be "fun" :)

greg k-h

  parent reply	other threads:[~2017-10-10  5:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 23:19 October, Paris, France - Meticulous In-person WireGuard Codebase Study Session 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
2017-10-10  6:10 ` Greg KH [this message]
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=20171010061054.GA7113@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --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.