From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Michael Ford <fanquake@gmail.com>
Cc: Wilko Meyer <w@wmeyer.eu>,
66968@debbugs.gnu.org, Leo Famulari <leo@famulari.name>
Subject: [bug#66968] [PATCH] gnu: linux-libre: add linux-libre-stable & linux-libre-longterm
Date: Fri, 13 Sep 2024 23:36:10 +0900 [thread overview]
Message-ID: <87wmjfwrhh.fsf@gmail.com> (raw)
In-Reply-To: <CAFyhPjW_ouvj8+_Fph4Rp838dqW8Re8dBx-5yjit5DxD0b=AXA@mail.gmail.com> (Michael Ford's message of "Mon, 6 Nov 2023 13:26:56 +0000")
Hello,
Michael Ford <fanquake@gmail.com> writes:
>>From dbe93718ea3dbae9d3e4795d0cea239cd3d6a674 Mon Sep 17 00:00:00 2001
> From: fanquake <fanquake@gmail.com>
> Date: Sun, 5 Nov 2023 18:31:55 +0000
> Subject: [PATCH] gnu: linux-libre: add linux-libre-stable &
> linux-libre-longterm
>
> A project I'm involved with would find it convenient to have pointers to
> the current stable / longterm kernel header branches, without having to
> specify an exact version. This way, we can point to i.e the longterm
> branch, and with each time-machine "bump", continue to have whatever the
> current longerm branch happens to be. So I'm submitting this patch for
> discussion / inclusion. Obviouly one overhead is remembering to keep
> these variables in sync whenever the status of the longterm/stable
> branches changes.
>
> * gnu/packages/linux (linux-libre-stable): New variable.
> (linux-libre-longerm): New variable.
> ---
> gnu/packages/linux.scm | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
> index 95a66e3d6a..a50526734e 100644
> --- a/gnu/packages/linux.scm
> +++ b/gnu/packages/linux.scm
> @@ -790,6 +790,8 @@ (define-public linux-libre-headers-5.15.49
>
> "13zqdcm4664vh7g57sxbfrlpsxm7zrma72mxdfdz7d9yndy2gfv8"))
>
> (define-public linux-libre-headers linux-libre-headers-5.15.49)
> +(define-public linux-libre-stable linux-libre-headers-6.5)
> +(define-public linux-libre-longterm linux-libre-headers-6.1)
Sounds like a reasonable thing to have. Leo, Wilko, what do you think?
Reviewed-by: Maxim Cournoyer <maxim.cournoyer@gmail>
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-09-13 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 13:26 [bug#66968] [PATCH] gnu: linux-libre: add linux-libre-stable & linux-libre-longterm Michael Ford
2024-09-13 14:36 ` Maxim Cournoyer [this message]
2024-09-13 15:50 ` Leo Famulari
2024-09-14 13:25 ` Maxim Cournoyer
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=87wmjfwrhh.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=66968@debbugs.gnu.org \
--cc=fanquake@gmail.com \
--cc=leo@famulari.name \
--cc=w@wmeyer.eu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.