unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Wilko Meyer <w@wmeyer.eu>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>, 70204@debbugs.gnu.org
Subject: [bug#70204] [PATCH 0/4] linux-libre kernel updates (2024-04-05)
Date: Thu, 4 Apr 2024 21:15:08 -0400	[thread overview]
Message-ID: <Zg9QnDXK0FfgdzoP@jasmine.lan> (raw)
In-Reply-To: <cover.1712270282.git.w@wmeyer.eu>

On Fri, Apr 05, 2024 at 12:43:01AM +0200, Wilko Meyer wrote:
> There have been updates to the 6.x series kernels again. Also 6.7 will
> be EoL soon according to this commit[0], which means I'll prepare a news
> entry and a patch for removal soon-ish.

Thanks! Already there were new releases for 6.8 and 6.6, so I replaced
that commits with newer updates and pushed to 'kernel-updates'.

I would interpret upstream's 6.7 announcement to mean that it's EoL now,
so I updated to 6.8 in a subsequent push that will get its own jobset:

https://ci.guix.gnu.org/jobset/kernel-updates

I'd recommend removing 6.7 after a week or so has passed.




  parent reply	other threads:[~2024-04-05  1:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 22:43 [bug#70204] [PATCH 0/4] linux-libre kernel updates (2024-04-05) Wilko Meyer
2024-04-04 22:50 ` [bug#70204] [PATCH 1/4] gnu: linux-libre 6.8: Update to 6.8.3 Wilko Meyer
2024-04-04 22:50 ` [bug#70204] [PATCH 2/4] gnu: linux-libre: Update to 6.7.12 Wilko Meyer
2024-04-04 22:50 ` [bug#70204] [PATCH 3/4] gnu: linux-libre 6.6: Update to 6.6.24 Wilko Meyer
2024-04-04 22:50 ` [bug#70204] [PATCH 4/4] gnu: linux-libre 6.1: Update to 6.1.84 Wilko Meyer
2024-04-05  1:15 ` Leo Famulari [this message]
2024-04-05 23:30   ` [bug#70204] [PATCH 0/4] linux-libre kernel updates (2024-04-05) Leo Famulari
2024-04-08 22:33 ` bug#70204: " Leo Famulari

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=Zg9QnDXK0FfgdzoP@jasmine.lan \
    --to=leo@famulari.name \
    --cc=70204@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --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 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).