From: John Kehayias <john.kehayias@protonmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Need people to help with kernel updates
Date: Mon, 09 Oct 2023 01:22:18 +0000 [thread overview]
Message-ID: <87pm1o8u9t.fsf@protonmail.com> (raw)
In-Reply-To: <ZSGdrpP_VJinXVmt@jasmine.lan>
Hi Leo,
On Sat, Oct 07, 2023 at 02:04 PM, Leo Famulari wrote:
> Hello,
>
> For a few years, I've been handling updates of the linux-libre kernel by
> myself. Now I want some more people to help with this.
>
Just wanted to say thanks for this work that goes on mostly behind the
scenes; I've never had any kernel hiccups related to Guix. Let's hope
I didn't just jinx that, but our rollbacks and generation selection at
boot actually make it a lot less painful to experiment here.
John
> The work itself is fairly mechanical and updates occur about once a
> week. It takes about 30 minutes to prepare the patches and push them to
> CI or send them to the mailing list.
>
> When a new major kernel version is released, then we also need to make a
> new kernel config file, which takes a few hours in total.
>
> There is plenty of support for the CI and QA infrastructure to build the
> kernels, so you don't need a powerful computer.
>
> This isn't the sort of the task that needs to be performed by a single
> person. The work could be spread, like most other packages in Guix.
>
> If you want to join in, please reply!
>
> Leo
next prev parent reply other threads:[~2023-10-09 1:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 18:04 Need people to help with kernel updates Leo Famulari
2023-10-07 18:31 ` Wilko Meyer
2023-10-08 18:12 ` Leo Famulari
2023-10-09 16:21 ` Wilko Meyer
2023-10-10 11:18 ` Leo Famulari
2023-10-10 14:13 ` wolf
2023-10-12 12:15 ` Wilko Meyer
2023-10-12 18:44 ` Leo Famulari
2023-10-15 19:58 ` Wilko Meyer
2023-10-28 20:17 ` Leo Famulari
2023-10-29 12:15 ` Wilko Meyer
2023-10-09 1:22 ` John Kehayias [this message]
2023-10-09 13:22 ` Luis Felipe
2023-10-14 15:48 ` Maxim Cournoyer
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=87pm1o8u9t.fsf@protonmail.com \
--to=john.kehayias@protonmail.com \
--cc=guix-devel@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 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).