Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Alex Davies <alex@davz.net>
To: Ilie Halip <ilie.halip@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] compat: support building for RHEL-8.2
Date: Sat, 1 Feb 2020 19:10:26 +0000	[thread overview]
Message-ID: <CAHwDNp0nBRsyksGMNyL-fLoY_5e2AQvqm2xTSSb=umPMXSZ3KQ@mail.gmail.com> (raw)
In-Reply-To: <CAHFW8PQ3=-f4aSxfSj1DEPxiM_yJgyiVubLmFdbGxYUDA_ST-w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 863 bytes --]

Hey All,

Its worth remembering that the RHEL release date and the CentOS release
dates are months part, for example:

RHEL 8.1 released: 5 Nov 2019
CentOS 8.1 released: ~15 Jan 2020

Much as I dont like this, the reality is that most RHEL/CentOS users will
not immediately upgrade to the "latest" kernel/release and even if they try
they cant for months unless they are paying RedHat money.

For what its worth, we are using our small influence as a paying
customer of RedHat (we have many thousands of host subscriptions) to ask
them to merge the (now upstream) upstream patches into RHEL8 (and then
manage it like everything else in their kernel), probably initially as a
Tech Preview, which is the real fix to this. If anybody else is also keen
to see this and is paying them, feel free to message me off-list and we can
get our TAMs to work together!

-Alex

[-- Attachment #1.2: Type: text/html, Size: 1071 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      reply	other threads:[~2020-02-01 19:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 11:18 Ilie Halip
2020-01-28 14:14 ` Jason A. Donenfeld
2020-01-30 13:54   ` Jason A. Donenfeld
2020-01-31  9:18     ` Ilie Halip
2020-02-01 19:10       ` Alex Davies [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='CAHwDNp0nBRsyksGMNyL-fLoY_5e2AQvqm2xTSSb=umPMXSZ3KQ@mail.gmail.com' \
    --to=alex@davz.net \
    --cc=ilie.halip@gmail.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).