From: Joe Doss <joe@solidadmin.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Procedure for Updating Snapshot
Date: Mon, 14 May 2018 09:50:17 -0500 [thread overview]
Message-ID: <b0c2fc11-7397-159a-7912-4bf0529aba37@solidadmin.com> (raw)
In-Reply-To: <27aed894-6521-7b2b-9148-d9d31f1dd62e@attglobal.net>
Hi Eddie,
On 05/14/2018 12:05 AM, Eddie wrote:
> Isn't that a little premature to drop support for CentOS 7.4. 7.5 was
> only officially released 3 days ago.
Snapshot 0.0.20180420 still supports CentOS 7.4, so support hasn't been
dropped. WireGuard is in active development and it would cause more pain
than it is worth to have to figure out how to get the current snapshot
working in both CentOS 7.4 and 7.5. A line has to be drawn somewhere to
keep development efforts moving forward.
Even if WireGuard was in the mainstream kernel, if you didn't update to
7.5 you would be running the older WireGuard code anyways. In my
experience upgrading between point releases in CentOS is pretty safe, so
I urge you do so if you feel you need the most recent WireGuard snapshot
working.
Joe
--
Joe Doss
joe@solidadmin.com
prev parent reply other threads:[~2018-05-14 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 20:21 Eddie
2018-05-13 21:29 ` Jason A. Donenfeld
2018-05-14 5:05 ` Eddie
2018-05-14 14:50 ` Joe Doss [this message]
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=b0c2fc11-7397-159a-7912-4bf0529aba37@solidadmin.com \
--to=joe@solidadmin.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).