unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: guix-devel@gnu.org
Subject: Re: Linux-Libre-LTS
Date: Thu, 24 Dec 2020 11:37:36 +0100	[thread overview]
Message-ID: <86bbed0c-3b57-f276-81a5-c0f1c1b6858e@web.de> (raw)
In-Reply-To: <877dp7ik5v.fsf@netris.org>

On 24.12.20 11:15, Mark H Weaver wrote:
>> Thoughts?
>
> I have one concern.
>
> It seems to me that the main reason to specify an LTS kernel is to avoid
> the unscheduled breakage that can occur when updating to a new kernel
> release series (i.e. to a new major+minor version).  Using
> "linux-libre-lts" would fail to avoid these unscheduled updates; it
> would merely reduce their frequency.
>
> The only way to reliably avoid unscheduled major+minor kernel updates is
> to specify "linux-libre-5.10" or similar.  The cost of this approach is
> trivial: editing a few characters in the OS configuration when one
> wishes to update to a newer LTS series.  The benefit is that the user
> gains control over when these updates will happen, and thus when any
> associated breakage will occur.
>
> To my mind, the benefit of this approach is so compelling, and its cost
> so trivial, that I can hardly understand why anyone who wishes to use an
> LTS kernel would choose otherwise.

It sums up, the more systems you maintain the more sums up this trivial
work. Defining "linux-libre-lts" is the same we do for Icecat or
Icedove. Yes, there can be breakage when they got update from one ESR
branch to the newer one.

So there are reasons to use always the newest LTS/ESR software version...

So I support this addition.


  reply	other threads:[~2020-12-24 10:37 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   ` Jonathan Brielmaier [this message]
2020-12-25  2:24     ` Linux-Libre-LTS Mark H Weaver
2020-12-27  5:24       ` Linux-Libre-LTS Leo Famulari
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=86bbed0c-3b57-f276-81a5-c0f1c1b6858e@web.de \
    --to=jonathan.brielmaier@web.de \
    --cc=guix-devel@gnu.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).