Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Bradley Saulteaux <bradsoto@protonmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard Windows ARM64 Build 21327
Date: Mon, 08 Mar 2021 09:25:40 +0000	[thread overview]
Message-ID: <kvwelbya-mAZJ2wfpt2vqF1O0GE7BwijqjtQjshHnNMooW7y_J8W6BgMKM65sGgZEWZQx7Zr4uejYiDkfL07ckiwZKqt2DR7BNrnJtXUsHs=@protonmail.com> (raw)
In-Reply-To: <CAHmME9q5HJ0QJMzqGBPjr-c4YSBcn3=JWjJB6BRAQtvzb02t6A@mail.gmail.com>

Hello Jason,

Yes prior to build 21327 the latest version worked.


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, March 7, 2021 8:49 AM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> Hi Bradley,
>
> Thanks for the report.
>
> > I'm not expecting my configuration to be supported or stressed over in the slightest.
>
> You are in fact very mistaken here. Having everything be broken and
> requiring you to resort to out of date versions is very much something
> that I'll stress over. Let's fix this.
>
> The first thing I'm wondering is:
>
> -   Did v0.3.8 work in builds prior to 21327, or did you never get a
>     chance to test v0.3.8 on other builds?
>
>     Jason
>



  reply	other threads:[~2021-03-08  9:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 20:29 Bradley Saulteaux
2021-03-07 15:49 ` Jason A. Donenfeld
2021-03-08  9:25   ` Bradley Saulteaux [this message]
2021-03-08 15:00     ` Jason A. Donenfeld
2021-03-20  2:33       ` Jason A. Donenfeld
2021-03-20  5:39         ` Bradley Saulteaux
2021-03-23  2:32           ` Jason A. Donenfeld
2021-03-23 22:21             ` Bradley Saulteaux

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='kvwelbya-mAZJ2wfpt2vqF1O0GE7BwijqjtQjshHnNMooW7y_J8W6BgMKM65sGgZEWZQx7Zr4uejYiDkfL07ckiwZKqt2DR7BNrnJtXUsHs=@protonmail.com' \
    --to=bradsoto@protonmail.com \
    --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).