From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: gentoo-user@lists.gentoo.org, Grant Edwards <grant.b.edwards@gmail.com>
Subject: [gentoo-user] Re: Slightly corrupted file systems when resuming from hibernation
Date: Wed, 17 Apr 2024 12:37:04 +0200 [thread overview]
Message-ID: <26143.42576.227523.275372@woitok.gmail.com> (raw)
In-Reply-To: Msg <uvmjd1$ntv$1@ciao.gmane.io> of 2024-04-16 19:26:25 -0000 from grant.b.edwards@gmail.com
Grant,
On Tuesday, 2024-04-16 19:26:25 -0000, you wrote:
> ...
> That means that all gentoo-sources stable kernels are "longterm"
> kernel versions on kernel.org. It does not mean that all "longterm"
> kernel versions from kernel.org are available as "stable" in
> gentoo-sources.
>
> It is a statement that "gentoo-sources stable" is a subset of
> "kernel.org longterm".
This sort of deteriorates into a debate about words rather than meanings
without explaining HOW LONG such a series of related kernels are main-
tained and provided. After all, "longterm" or "LTS" suggest that these
lines of developement are less short-lived than others. To give an ex-
ample: the oldest "longterm" kernels listed on "kernel.org" are 4.19.*,
5.4.* and 5.10.*. Of these only 5.10.* is still available from Gentoo.
Digging through my Gentoo installation logs, I can see that 4.19.72 was
one of the first kernels I built myself. This was somewhen in the mid-
dle of 2019, that is, not yet five years back. And this kernel line has
already vanished from Gentoo. So what time span are we talking about
when we say "LTS Gentoo kernel"? Roughly four, three or two years? And
why is the support provided by Gentoo significantly shorter than that by
"kernel.org"?
Sincerely,
Rainer
next prev parent reply other threads:[~2024-04-17 10:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 17:46 [gentoo-user] Slightly corrupted file systems when resuming from hibernation Dr Rainer Woitok
2024-04-14 18:41 ` [gentoo-user] " Dr Rainer Woitok
2024-04-15 11:48 ` Michael
2024-04-16 9:04 ` Dr Rainer Woitok
2024-04-16 10:15 ` Michael
2024-04-16 13:29 ` Dr Rainer Woitok
2024-04-16 13:53 ` Arve Barsnes
2024-04-16 14:53 ` Grant Edwards
2024-04-16 15:07 ` Dale
2024-04-16 15:01 ` Dale
2024-04-16 15:14 ` Grant Edwards
2024-04-16 16:43 ` Dr Rainer Woitok
2024-04-16 19:26 ` Grant Edwards
2024-04-17 9:10 ` Michael
2024-04-17 13:52 ` Grant Edwards
2024-04-17 20:05 ` Dale
2024-04-17 20:32 ` Grant Edwards
2024-04-17 22:18 ` Dale
2024-04-17 15:50 ` Dr Rainer Woitok
2024-04-17 17:52 ` Wols Lists
2024-04-17 10:37 ` Dr Rainer Woitok [this message]
2024-04-17 10:56 ` Michael
2024-04-17 14:11 ` Grant Edwards
2024-04-17 16:11 ` Dr Rainer Woitok
2024-04-17 17:53 ` Grant Edwards
2024-04-16 10:55 ` Dale
2024-04-16 11:15 ` Michael
2024-04-16 12:48 ` Dale
2024-04-16 14:32 ` Jack
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=26143.42576.227523.275372@woitok.gmail.com \
--to=rainer.woitok@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=grant.b.edwards@gmail.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