From: Leo Famulari <leo@famulari.name>
To: Wilko Meyer <w@wmeyer.eu>
Cc: 67016-done@debbugs.gnu.org
Subject: [bug#67016] [PATCH 1/7] gnu: linux-libre 6.5: Update to 6.5.11.
Date: Tue, 14 Nov 2023 00:14:58 -0500 [thread overview]
Message-ID: <ZVMCUhPvdEiFI3k_@jasmine.lan> (raw)
In-Reply-To: <ZVMBmN91tUeiYyY4@jasmine.lan>
On Tue, Nov 14, 2023 at 12:11:52AM -0500, Leo Famulari wrote:
> On Thu, Nov 09, 2023 at 02:28:42PM +0100, Wilko Meyer wrote:
> > * gnu/packages/linux.scm (linux-libre-6.5-version): Update to 6.5.11.
> > (linux-libre-6.5-pristine-source): Update hash.
>
> Pushed as c9255451b549f2999b83aa344d2412802225adf8, thanks!
I forgot to sign before attempting to push, and so this patch series was
actually pushed as 8074235a7e820ab6dd61179be3f73bf7ef85b1aa
Sorry for the confusion!
next prev parent reply other threads:[~2023-11-14 5:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 13:26 [bug#67016] [PATCH 0/7] linux-libre kernel updates (2023-11-09) Wilko Meyer
2023-11-09 13:28 ` [bug#67016] [PATCH 1/7] gnu: linux-libre 6.5: Update to 6.5.11 Wilko Meyer
2023-11-09 13:28 ` [bug#67016] [PATCH 2/7] gnu: linux-libre 6.1: Update to 6.1.62 Wilko Meyer
2023-11-09 13:28 ` [bug#67016] [PATCH 3/7] gnu: linux-libre 5.15: Update to 5.15.138 Wilko Meyer
2023-11-09 13:28 ` [bug#67016] [PATCH 4/7] gnu: linux-libre 5.10: Update to 5.10.200 Wilko Meyer
2023-11-09 13:28 ` [bug#67016] [PATCH 5/7] gnu: linux-libre 5.4: Update to 5.4.260 Wilko Meyer
2023-11-09 13:28 ` [bug#67016] [PATCH 6/7] gnu: linux-libre 4.19: Update to 4.19.298 Wilko Meyer
2023-11-09 13:28 ` [bug#67016] [PATCH 7/7] gnu: linux-libre 4.14: Update to 4.14.329 Wilko Meyer
2023-11-10 18:36 ` [bug#67016] [PATCH 1/7] gnu: linux-libre 6.5: Update to 6.5.11 Leo Famulari
2023-11-11 7:32 ` Leo Famulari
2023-11-14 1:00 ` Leo Famulari
2023-11-15 10:02 ` Wilko Meyer
2023-11-14 5:11 ` bug#67016: " Leo Famulari
2023-11-14 5:14 ` Leo Famulari [this message]
2023-11-14 0:53 ` [bug#67016] [PATCH v2 1/9] " Leo Famulari
2023-11-14 0:53 ` [bug#67016] [PATCH v2 2/9] gnu: linux-libre 6.1: Update to 6.1.62 Leo Famulari
2023-11-14 0:53 ` [bug#67016] [PATCH v2 3/9] gnu: linux-libre 5.15: Update to 5.15.138 Leo Famulari
2023-11-14 0:53 ` [bug#67016] [PATCH v2 4/9] gnu: linux-libre 5.10: Update to 5.10.200 Leo Famulari
2023-11-14 0:53 ` [bug#67016] [PATCH v2 5/9] gnu: linux-libre 5.4: Update to 5.4.260 Leo Famulari
2023-11-14 0:53 ` [bug#67016] [PATCH v2 6/9] gnu: linux-libre 4.19: Update to 4.19.298 Leo Famulari
2023-11-14 0:53 ` [bug#67016] [PATCH v2 7/9] gnu: linux-libre 4.14: Update to 4.14.329 Leo Famulari
2023-11-14 0:53 ` [bug#67016] [PATCH v2 8/9] gnu: Add linux-libre 6.6.1 Leo Famulari
2023-11-14 0:54 ` [bug#67016] [PATCH v2 9/9] gnu: Make linux-libre 6.6 the default 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=ZVMCUhPvdEiFI3k_@jasmine.lan \
--to=leo@famulari.name \
--cc=67016-done@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).