From: Willy Tarreau <w@1wt.eu>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Mark Brown <broonie@kernel.org>,
linux-toolchains@vger.kernel.org,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: gcc 5 & 6 & others already out of date?
Date: Thu, 13 Oct 2022 18:51:55 +0200 [thread overview]
Message-ID: <20221013165155.GJ16609@1wt.eu> (raw)
In-Reply-To: <Y0g+wTTJmlaFVLzr@zx2c4.com>
On Thu, Oct 13, 2022 at 10:37:21AM -0600, Jason A. Donenfeld wrote:
> On Thu, Oct 13, 2022 at 05:26:04PM +0100, Mark Brown wrote:
> > Note that I'm not saying we shouldn't upgrade our requirements at all,
> > just that I'm worrying about going from one extreme to the other in
> > terms of version requirements - it feels like there's a step change when
> > you move from things you can get in current release distros people are
> > likely to be using to things that will require a large proportion of
> > people to install extra stuff. At the minute we're more at the other
> > end where it can be hard to figure out who'd even have the oldest
> > versions we support without deliberately seeking them out and keeping
> > them going is noticably making work for people.
>
> Regarding "one extreme to the other", I suspect that in spite of my
> arguments, which would seem to justify an extreme, the actual thing I
> suggested is a bit more moderate: let's support the latest 2 or 3 gccs
> at the time of kernel release. If we choose 3, that's roughly 3 years of
> gccs, right?
Ideally we should support at the very least those of the oldest
supported LTS kernels, because one thing for LTS users is that we
also want to encourage them to try new kernels, and if they can't
build newer kernels from the start we all know they'll give up
very quickly. And this eases the backport to those kernels as it
is expected that a mainline fix will support those versions (even
if it may break from time to time by accident, but the intent is
there).
> 3 years seems like a fairly long amount of time.
For a developer changing their distro every 6 months, possibly. Not
for users who took time to stabilize their system to something working
and who are curious about what the new kernel provides from time to
time.
Willy
next prev parent reply other threads:[~2022-10-13 16:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 1:36 gcc 5 & 6 & others already out of date? Jason A. Donenfeld
2022-10-13 12:22 ` David Laight
2022-10-13 12:59 ` Mark Brown
2022-10-13 15:23 ` Jason A. Donenfeld
2022-10-13 16:18 ` Willy Tarreau
2022-10-14 4:28 ` David Laight
2022-10-14 5:27 ` Willy Tarreau
2022-10-13 16:26 ` Mark Brown
2022-10-13 16:37 ` Jason A. Donenfeld
2022-10-13 16:51 ` Willy Tarreau [this message]
2022-10-13 17:16 ` Mark Brown
2022-10-13 18:38 ` Florian Weimer
2022-10-13 20:23 ` Mark Brown
2022-10-14 6:15 ` Florian Weimer
2022-10-13 18:39 ` Florian Weimer
2022-10-13 21:03 ` Nick Desaulniers
2022-10-14 6:37 ` Florian Weimer
2022-10-13 21:08 ` Nick Desaulniers
2022-10-14 1:31 ` Jason A. Donenfeld
2022-10-14 11:13 ` Mark Brown
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=20221013165155.GJ16609@1wt.eu \
--to=w@1wt.eu \
--cc=Jason@zx2c4.com \
--cc=broonie@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
/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).