From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>,
guix-devel <guix-devel@gnu.org>,
guix-science@gnu.org
Cc: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: Doing away with CentOS 6 support (Linux faux-2.6)?
Date: Fri, 08 Dec 2023 17:54:22 +0100 [thread overview]
Message-ID: <87v8987hz5.fsf@gmail.com> (raw)
In-Reply-To: <87msulbpgl.fsf@inria.fr>
Hi,
On Thu, 07 Dec 2023 at 23:46, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
> Back in 2018, this was deemed important for HPC clusters, where CentOS 6
> was then relatively common, as Ricardo explained:
Héhé! A colleague re-installed CentOS 6 this week; for testing
purpose. Hum… :-)
> Five years later, it seems reasonable to drop the patch (which is likely
> untested these days). If you disagree, now’s the time to make your
> voice heard!
Yeah, let drop this patch. Well, CentOS 7 will be soon end of life so
it seems very reasonable to drop patches for CentOS 6 only.
Cheers,
simon
prev parent reply other threads:[~2023-12-08 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 22:46 Doing away with CentOS 6 support (Linux faux-2.6)? Ludovic Courtès
2023-12-08 16:54 ` Simon Tournier [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8987hz5.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix-science@gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=ricardo.wurmus@mdc-berlin.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).