Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Joshua Sjoding <joshua.sjoding@scjalliance.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard for Windows failed to start after update to v0.2.1
Date: Thu, 19 Nov 2020 11:39:11 -0800	[thread overview]
Message-ID: <CALaUSuvO4Tt4aa16BM0VihAqSBcKuF=Mxfo7m4Y5L2KkRurEkg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pBVYY+eGzFtgZKY-1FfL8gVNJXAZ3PadtkyEsuUU55=A@mail.gmail.com>

I ran WireGuard for Windows version 0.2.2 all day yesterday and I've
been running 0.2.3 today. Since the 0.2.2 release we've had no issues
with the update process.

If we run into any more issues we'll let you know. If you don't hear
back you can assume all is well.

Cheers!

Joshua Sjoding
SCJ Alliance
IT Specialist
www.scjalliance.com
On Wed, Nov 18, 2020 at 5:41 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hi Joshua,
>
> A new version is now released, which should address all the issues you
> found. Let me know how things go...
>
> Jason

  reply	other threads:[~2020-11-19 19:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 17:46 Joshua Sjoding
2020-11-17 20:59 ` Jason A. Donenfeld
2020-11-17 21:19   ` Joshua Sjoding
2020-11-17 21:56     ` Jason A. Donenfeld
2020-11-17 22:03       ` Jason A. Donenfeld
2020-11-17 22:05         ` Jason A. Donenfeld
2020-11-17 22:46       ` Joshua Sjoding
2020-11-18  0:05         ` Jason A. Donenfeld
2020-11-18  0:42           ` Jason A. Donenfeld
2020-11-18 13:41             ` Jason A. Donenfeld
2020-11-19 19:39               ` Joshua Sjoding [this message]
2020-11-19 20:00                 ` 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='CALaUSuvO4Tt4aa16BM0VihAqSBcKuF=Mxfo7m4Y5L2KkRurEkg@mail.gmail.com' \
    --to=joshua.sjoding@scjalliance.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).