From: Leo Famulari <leo@famulari.name>
To: Wilko Meyer <w@wmeyer.eu>
Cc: 66455@debbugs.gnu.org
Subject: [bug#66455] [PATCH 0/8] linux-libre kernel updates
Date: Tue, 10 Oct 2023 22:59:51 -0400 [thread overview]
Message-ID: <ZSYPpxFXpUKeTL_q@jasmine.lan> (raw)
In-Reply-To: <20231010231017.6599-1-w@wmeyer.eu>
On Wed, Oct 11, 2023 at 01:10:17AM +0200, Wilko Meyer wrote:
> Wilko Meyer (8):
> gnu: linux-libre 6.5: Update to 6.5.7.
> gnu: linux-libre 6.1: Update to 6.1.57.
> gnu: linux-libre 5.15: Update to 5.15.135.
> gnu: linux-libre 5.10: Update to 5.10.198.
> gnu: linux-libre 5.4: Update to 5.4.258.
> gnu: linux-libre 4.19: Update to 4.19.296.
> gnu: linux-libre 4.14: Update to 4.14.327.
> gnu: Update my copyright.
Thanks! Pushed to the 'kernel-updates' branch so that CI will build
them:
https://git.savannah.gnu.org/cgit/guix.git/log/?h=kernel-updates
https://ci.guix.gnu.org/jobset/kernel-updates
prev parent reply other threads:[~2023-10-11 3:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 23:10 [bug#66455] [PATCH 0/8] linux-libre kernel updates Wilko Meyer
2023-10-10 23:16 ` [bug#66455] [PATCH 1/8] gnu: linux-libre 6.5: Update to 6.5.7 Wilko Meyer
2023-10-10 23:16 ` [bug#66455] [PATCH 2/8] gnu: linux-libre 6.1: Update to 6.1.57 Wilko Meyer
2023-10-10 23:16 ` [bug#66455] [PATCH 3/8] gnu: linux-libre 5.15: Update to 5.15.135 Wilko Meyer
2023-10-10 23:16 ` [bug#66455] [PATCH 4/8] gnu: linux-libre 5.10: Update to 5.10.198 Wilko Meyer
2023-10-10 23:16 ` [bug#66455] [PATCH 5/8] gnu: linux-libre 5.4: Update to 5.4.258 Wilko Meyer
2023-10-10 23:16 ` [bug#66455] [PATCH 6/8] gnu: linux-libre 4.19: Update to 4.19.296 Wilko Meyer
2023-10-10 23:16 ` [bug#66455] [PATCH 7/8] gnu: linux-libre 4.14: Update to 4.14.327 Wilko Meyer
2023-10-10 23:16 ` [bug#66455] [PATCH 8/8] gnu: Update my copyright Wilko Meyer
2023-10-12 18:45 ` bug#66455: [PATCH 1/8] gnu: linux-libre 6.5: Update to 6.5.7 Leo Famulari
2023-10-11 2:59 ` Leo Famulari [this message]
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=ZSYPpxFXpUKeTL_q@jasmine.lan \
--to=leo@famulari.name \
--cc=66455@debbugs.gnu.org \
--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).