From: Wilko Meyer <w@wmeyer.eu>
To: Leo Famulari <leo@famulari.name>
Cc: Wilko Meyer <w@wmeyer.eu>, 66841@debbugs.gnu.org
Subject: bug#66841: [PATCH v2] gnu: Add linux-libre 6.6.
Date: Mon, 06 Nov 2023 23:41:47 +0100 [thread overview]
Message-ID: <878r7abiwv.fsf@wmeyer.eu> (raw)
In-Reply-To: <ZUaTFp4h2NSmF_bs@jasmine.lan>
Hi Leo,
Leo Famulari <leo@famulari.name> writes:
> I think it's helpful to wait a couple days before doing that after
> adding the new kernel series. This gives people a chance to test things
> to before we deploy the update for all users.
Agreed, thanks for mentioning this! I'll send a v3 of this patch series
that splits up the changes in two commits; one introducing 6.6, the
other making it the default kernel (which can be applied after a couple
of days if 6.6 works well and as expected). WDYT?
--
Kind regards,
Wilko Meyer
w@wmeyer.eu
next prev parent reply other threads:[~2023-11-06 23:25 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 [this message]
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 ` bug#66841: [PATCH v4 1/3] gnu: Add linux-libre 6.6 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878r7abiwv.fsf@wmeyer.eu \
--to=w@wmeyer.eu \
--cc=66841@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.