From: Bert Vermeulen <bert@biot.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard @ FOSDEM -- Meetup
Date: Sat, 26 Jan 2019 10:30:57 +0100 [thread overview]
Message-ID: <d9fb0c7a-b74f-a4e0-2daa-557adc09c990@biot.com> (raw)
In-Reply-To: <CAHmME9oWcFMquF4TuaQ3o1KVN2pBwr4+uyJx4=ujGVtzexzqzw@mail.gmail.com>
On 01/25/2019 07:28 PM, Jason A. Donenfeld wrote:
> Hey folks,
>
> I think I'll head to FOSDEM next weekend. Is there interest on the
> list in some sort of meetup and discussion there? If so, is somebody
> who's familiar with the FODEM ins-and-outs willing to work out finding
> a room and scheduling?
Jason,
You're several months too late for that. However, it's not uncommon for
"unofficial" developer teams to just occupy a table in one of the
cafetarias, and just meet up there for however long they want.
--
Bert Vermeulen
bert@biot.com
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-01-26 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 18:28 WireGuard @ FOSDEM -- Meetup Jason A. Donenfeld
2019-01-26 9:30 ` Bert Vermeulen [this message]
2019-01-26 9:50 ` Germano Massullo
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=d9fb0c7a-b74f-a4e0-2daa-557adc09c990@biot.com \
--to=bert@biot.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).