unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Linux-Libre-LTS
Date: Sun, 27 Dec 2020 00:24:49 -0500	[thread overview]
Message-ID: <X+gaoau8I/57Ej4X@jasmine.lan> (raw)
In-Reply-To: <877dp6ipw3.fsf@netris.org>

[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]

On Thu, Dec 24, 2020 at 09:24:17PM -0500, Mark H Weaver wrote:
> What do you think?

I understand your concerns about the ambiguous meaning of an "LTS"
kernel in the context of Guix.

In order to make it more concrete, we could attempt to stay on the same
long-term support kernel series between Guix releases. It might not
always be possible or convenient, but it could make it more meaningful.
If the LTS kernel were to expire before a new Guix release, we would
have to decide what to do. We shouldn't start backporting fixes or
maintaining our own tree, in any case.

Regarding the comment above the new variables, I think that the longterm
support kernels are, by definition, "current". If they are not current,
then they are not supported. If the variables should point to the newest
kernel with longterm support, let's change the comment.

Something to note is that, much of the time, Guix *only* offers
long-term support kernels.

Also, the dates on <https://jxself.org/linux-libre/> appear to have
drifted out of sync with the upstream at
<https://www.kernel.org/category/releases.html>.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-12-27  5:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  3:32 Linux-Libre-LTS Raghav Gururajan
2020-10-29  7:47 ` Linux-Libre-LTS Efraim Flashner
2020-11-03  3:41   ` Linux-Libre-LTS Raghav Gururajan
2020-12-24  3:54   ` Linux-Libre-LTS Raghav Gururajan
2020-12-26 18:09     ` Linux-Libre-LTS Efraim Flashner
2020-10-29  8:24 ` Linux-Libre-LTS Tobias Geerinckx-Rice
2020-10-29 14:16   ` Linux-Libre-LTS Leo Famulari
2020-11-03  3:44   ` Linux-Libre-LTS Raghav Gururajan
2020-11-03 10:56     ` Linux-Libre-LTS Tobias Geerinckx-Rice
2020-11-03 19:54       ` Linux-Libre-LTS Raghav Gururajan
2020-11-03 20:06         ` Linux-Libre-LTS Tobias Geerinckx-Rice
2020-12-24 10:15 ` Linux-Libre-LTS Mark H Weaver
2020-12-24 10:37   ` Linux-Libre-LTS Jonathan Brielmaier
2020-12-25  2:24     ` Linux-Libre-LTS Mark H Weaver
2020-12-27  5:24       ` Leo Famulari [this message]
2020-12-27 13:27       ` Linux-Libre-LTS Bengt Richter
2020-12-27 17:09   ` Linux-Libre-LTS Raghav Gururajan
2020-12-29 20:52     ` Linux-Libre-LTS Leo Famulari
2020-12-30 16:08       ` Linux-Libre-LTS Raghav Gururajan
2020-12-30 21:18         ` Linux-Libre-LTS Raghav Gururajan
2020-12-31  0:24           ` Linux-Libre-LTS Leo Famulari
2020-12-31  3:19           ` Linux-Libre-LTS Leo Famulari
2020-12-30 15:47 ` Linux-Libre-LTS Jonathan Brielmaier

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=X+gaoau8I/57Ej4X@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).