From: Sebastian Gottschall <s.gottschall@newmedia-net.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
David Kricker <logcabin@fastmail.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] WireGuard Snapshot `0.0.20181007` Available
Date: Wed, 10 Oct 2018 00:29:21 +0200 [thread overview]
Message-ID: <a276382e-b6c7-bd7d-2e70-23f81177876c@newmedia-net.de> (raw)
In-Reply-To: <CAHmME9pbcPFghexTJnZz0kqJvTwa_bxpnox1vho8rMTQWd_pCQ@mail.gmail.com>
i do not use the defined master. i just checkout the git revisions
defined by your snapshots. but since you release snapshots 2 times per
week sometimes its still ends up on a heavy changing module
but that should not be the topic here. the topic is what leads wireguard
to fail on his system. so we need to track down first which hardware he
is using since i do support alot of devices with alot of different cpu
platforms. so please stay on topic and do not speculate too much
Am 09.10.2018 um 21:18 schrieb Jason A. Donenfeld:
> On Tue, Oct 9, 2018 at 6:30 PM Sebastian Gottschall
> <s.gottschall@newmedia-net.de> wrote:
>> just to make sure. since i'm updating wireguard in dd-wrt very often to the latest state of art code from git.
> Do not do this. Rather, use snapshots. If you're distributing builds
> based on git master, you're putting your users at unnecessary risk.
> The only safe and acceptable distribution of WireGuard is using the
> latest snapshot tarball. When you use git master, you're not getting
> the "latest state of art code", you're getting "jason's 5am
> force-pushes and wacky ideas pre-codereview." On the other hand, when
> you use snapshots, you're getting code that I've spent some time
> reviewing and double checking to make sure it won't murder kittens and
> related atrocities.
>
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2018-10-09 22:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 15:20 [ANNOUNCE] WireGuard Snapshot `0.0.20181007` Available Jason A. Donenfeld
2018-10-07 20:49 ` Jordan Glover
2018-10-07 22:37 ` Jason A. Donenfeld
2018-10-07 22:43 ` logcabin
2018-10-07 22:50 ` Jason A. Donenfeld
2018-10-09 22:29 ` Sebastian Gottschall [this message]
2018-10-08 11:59 ` Jordan Glover
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=a276382e-b6c7-bd7d-2e70-23f81177876c@newmedia-net.de \
--to=s.gottschall@newmedia-net.de \
--cc=Jason@zx2c4.com \
--cc=logcabin@fastmail.net \
--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).