From: Reto <reto@labrat.space>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Rachel Kroll <rachelbythebay@gmail.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: "Wireguard [sic]: great protocol, but skip the Mac app" blog post
Date: Sat, 26 Dec 2020 11:32:02 +0100 [thread overview]
Message-ID: <20201226103202.q2netyh65ymfmbel@feather.localdomain> (raw)
In-Reply-To: <CAHmME9qUN7qTRGU3mFTGHZVGPXE-csdojziZQ-kX460W7pssJw@mail.gmail.com>
Hi Jason,
Please don't let blog posts like this get to you.
Following this list, as well as the IRC channel, it's very clear that you care
and go over great pains to make wireguard useful to all.
Rest assured that a lot of people, including me, are very grateful for all that
you do and for your nice work all over the place in the kernel.
I don't write blog posts that trend on hacker news I'm afraid... So this email
has to do ;)
Kind regards,
Reto
next prev parent reply other threads:[~2020-12-26 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 15:48 Jason A. Donenfeld
2020-12-26 10:32 ` Reto [this message]
2020-12-27 17:37 ` Peter Korsgaard
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=20201226103202.q2netyh65ymfmbel@feather.localdomain \
--to=reto@labrat.space \
--cc=Jason@zx2c4.com \
--cc=rachelbythebay@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).