From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: snapshot 0.0.20170628 broken?
Date: Thu, 29 Jun 2017 21:34:14 +0200 [thread overview]
Message-ID: <CAHmME9qrxXFXj4_G_-spg2D5SqUrmnJeV-8ei6jQXku-Hf1COA@mail.gmail.com> (raw)
In-Reply-To: <15cf5049001.efa4dc9c195686.3384309935944529785@hda.me>
This issue has been fixed in the snapshot I just published.
next prev parent reply other threads:[~2017-06-29 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 18:02 snapshot 0.0.20170628 broken? HDA
2017-06-29 19:34 ` Jason A. Donenfeld [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-29 16:14 HDA
2017-06-29 16:32 ` Reuben Martin
2017-06-29 15:47 Reuben Martin
2017-06-29 16:39 ` Jason A. Donenfeld
2017-06-29 16:41 ` Kalin KOZHUHAROV
2017-06-29 16:42 ` Jason A. Donenfeld
2017-06-29 16:47 ` Kalin KOZHUHAROV
2017-06-29 17:23 ` Reuben Martin
2017-06-29 17:23 ` 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=CAHmME9qrxXFXj4_G_-spg2D5SqUrmnJeV-8ei6jQXku-Hf1COA@mail.gmail.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.