From: Laura Smith <n5d9xq3ti233xiyif2vp@protonmail.ch>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: Two small Wireguard frustrations on Mac & Apple iOS
Date: Thu, 08 Oct 2020 14:04:58 +0000 [thread overview]
Message-ID: <5DdCbxbxbLZBsJ4N5L4HkYoefn_KpBSk-UWlIM52Rd7uOlbYwKjkzudKbnInh2aSFOUG0xmFFhGvYLvzm_Xtmpfo22Vpmwr0buAnaMOHDBQ=@protonmail.ch> (raw)
In-Reply-To: <CAHmME9qZcWfVGaJ210e3XLW60NhZY403CEve7YK+E7nfcJEyXQ@mail.gmail.com>
> You're free to do that, and I'd generally prefer that instead of
> having this mailing list turning into a place for you to vent your
> frustration. These bugs are non-trivial. If you want to put some
> development hours on it, we'd love to have your contributions.
> Otherwise you'll have to wait for one of us. That's just how it goes,
> and venting probably won't make it happen faster.
Jason,
Let me put it more simply.
I understand the whole development lifecycle thing, I really do.
My point is all that was needed was an ack.
I first posted about this issue to list on Sun Aug 23 20:34:17 CEST 2020.
After that post, the only thing I have seen is posts from other people saying "yes, I've seen that too on my system". That's great from my perspective, in terms of showing I'm not the only one, but not so great in terms of fix.
A one-line ack from you (or someone else) saying "yup, seen this, currently busy on $android_or_whatever" would have been more than sufficient.
Instead, all I saw was radio silence which can be openly interpreted ....
Laura.
next prev parent reply other threads:[~2020-10-08 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 18:34 Two small Wireguard frustrations on Mac & Apple iOS Laura Smith
2020-08-27 8:29 ` Alexander Burke
2020-09-11 1:08 ` Eddie Jones
2020-09-28 12:59 ` Laura Smith
2020-09-28 13:20 ` Jonny
2020-09-28 13:53 ` Jeff Squyres
[not found] ` <CAPMuNSpqK6BOL4h9zkSNyEO4UJroDDMnU5GJprvAyDeTdXW=kw@mail.gmail.com>
2020-09-28 20:49 ` Dimitri J. Panagiotou
2020-09-30 1:25 ` Jeff Squyres
2020-10-01 1:04 ` Brian Gregory
2020-10-01 11:17 ` Jason A. Donenfeld
2020-10-08 14:04 ` Laura Smith [this message]
[not found] ` <a473a088-91f8-10bb-7522-67c989c7a052@k8s.local>
2020-09-15 23:29 ` Eddie Jones
2020-10-01 11:14 ` Jason A. Donenfeld
2020-10-01 11:23 ` Jasper Knockaert
2020-10-01 11:57 ` Jason A. Donenfeld
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='5DdCbxbxbLZBsJ4N5L4HkYoefn_KpBSk-UWlIM52Rd7uOlbYwKjkzudKbnInh2aSFOUG0xmFFhGvYLvzm_Xtmpfo22Vpmwr0buAnaMOHDBQ=@protonmail.ch' \
--to=n5d9xq3ti233xiyif2vp@protonmail.ch \
--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 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).