From: Leo Famulari <leo@famulari.name>
To: Wilko Meyer <w@wmeyer.eu>
Cc: 66841@debbugs.gnu.org
Subject: bug#66841: [PATCH v4 1/3] gnu: Add linux-libre 6.6.
Date: Fri, 10 Nov 2023 13:35:48 -0500 [thread overview]
Message-ID: <ZU54BA6wWXL_wPW_@jasmine.lan> (raw)
In-Reply-To: <20231109145802.27899-1-w@wmeyer.eu>
On Thu, Nov 09, 2023 at 03:57:36PM +0100, Wilko Meyer wrote:
> * gnu/packages/linux.scm (linux-libre-6.6-version, linux-libre-6.6-gnu-revision,
> deblob-scripts-6.6, linux-libre-6.6-pristine-source, linux-libre-6.5-source,
> linux-libre-headers-6.6, linux-libre-6.6): New variables.
> * gnu/packages/aux-files/linux-libre/6.6-x86_64.conf: New file.
> * Makefile.am (AUX_FILES): Add 6.6-x86_64.conf.
Thanks!
I squashed the "Add 6.6" and "Update to 6.6.1" commits into a single
commit, and then pushed to 'kernel-updates' along with the other updates
you sent in #67016.
prev parent reply other threads:[~2023-11-10 18:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 0:26 bug#66841: [PATCH 0/1] WIP: linux-libre 6.6 Wilko Meyer
2023-10-31 0:29 ` bug#66841: [PATCH 1/1] gnu: Add " Wilko Meyer
2023-11-14 5:11 ` Leo Famulari
2023-11-14 5:16 ` Leo Famulari
2023-11-01 14:32 ` bug#66841: [PATCH v2] " Wilko Meyer
2023-11-04 18:51 ` Leo Famulari
2023-11-04 18:53 ` Leo Famulari
2023-11-06 22:41 ` Wilko Meyer
2023-11-09 3:23 ` Leo Famulari
2023-11-09 14:59 ` Wilko Meyer
2023-11-07 19:02 ` bug#66841: [PATCH v3 1/2] " Wilko Meyer
2023-11-07 19:02 ` bug#66841: [PATCH v3 2/2] gnu: Make linux-libre 6.6 the default Wilko Meyer
2023-11-09 14:57 ` bug#66841: [PATCH v4 1/3] gnu: Add linux-libre 6.6 Wilko Meyer
2023-11-09 14:57 ` bug#66841: [PATCH v4 2/3] gnu: Make linux-libre 6.6 the default Wilko Meyer
2023-11-09 14:57 ` bug#66841: [PATCH v4 3/3] gnu: linux-libre 6.6: Update to 6.6.1 Wilko Meyer
2023-11-10 18:35 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZU54BA6wWXL_wPW_@jasmine.lan \
--to=leo@famulari.name \
--cc=66841@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 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.