From: Michael Hudson-Doyle <michael.hudson@canonical.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: Stefan Liebler <stli@linux.ibm.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Question: Is there a plan when to require a higher Linux kernel version than 3.2?
Date: Thu, 22 Sep 2022 11:07:04 +1200 [thread overview]
Message-ID: <CAJ8wqtc7i5deoH0CH5Ek+A82u6-rPCEkc4-dmS2pTH2gqxFJ0w@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2209211640120.57900@digraph.polyomino.org.uk>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Thu, 22 Sept 2022 at 04:50, Joseph Myers <joseph@codesourcery.com> wrote:
> * The oldest kernel version supported on
> https://www.kernel.org/category/releases.html (currently 4.9) being new
> enough for the change to allow significant cleanups in glibc.
>
I don't know how seriously you are suggesting moving the baseline to 4.9 or
on what timeframe, but we (Canonical) still have Ubuntu 14.04 (kernel 3.13)
in extended support until 2024 and 16.04 (kernel 4.4) until 2026 and we
would like these users to be able to use newer distributions in containers
(I don't know RHEL's policies, but by my reading RHEL7, based on kernel
3.10, is in a similar kind of extended support until 2026). So I don't want
to hold up progress to a new and better world too much... but also there is
a reason to move slowly here.
Cheers,
mwh
next prev parent reply other threads:[~2022-09-21 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 9:11 Stefan Liebler
2022-09-20 9:40 ` Xi Ruoyao
2022-09-20 9:56 ` Stefan Liebler
2022-09-21 16:50 ` Joseph Myers
2022-09-21 23:07 ` Michael Hudson-Doyle [this message]
2022-09-22 16:59 ` Joseph Myers
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=CAJ8wqtc7i5deoH0CH5Ek+A82u6-rPCEkc4-dmS2pTH2gqxFJ0w@mail.gmail.com \
--to=michael.hudson@canonical.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=stli@linux.ibm.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 read-only IMAP folder(s) and NNTP newsgroup(s).