From: "Ludovic Courtès" <ludo@gnu.org>
To: Lilah Tascheter <lilah@lunabee.space>
Cc: guix-devel@gnu.org, Efraim Flashner <efraim@flashner.co.il>,
Vagrant Cascadian <vagrant@debian.org>,
Christopher Baines <guix@cbaines.net>,
Josselin Poiret <dev@jpoiret.xyz>,
Mathieu Othacehe <othacehe@gnu.org>,
Simon Tournier <zimon.toutoune@gmail.com>,
Tobias Geerinckx-Rice <me@tobias.gr>
Subject: Re: Call for testers for bootloader subsystem rewrite!
Date: Mon, 12 Aug 2024 16:28:15 +0200 [thread overview]
Message-ID: <87mslhbytc.fsf@gnu.org> (raw)
In-Reply-To: <6fdee15ed17de430adc03fde31bfc24dce43b85c.camel@lunabee.space> (Lilah Tascheter's message of "Sat, 03 Aug 2024 23:09:53 -0500")
Hi Lilah,
Lilah Tascheter <lilah@lunabee.space> skribis:
> I just submitted a patchset containing a full rewrite of Guix's
> bootloader subsystem, as in its current state, it was only really meant
> to support GRUB. Seeing as we support a large variety of bootloaders,
> and a bug in this subsystem could be disasterous, I figured I'd ask for
> testers here.
>
> So, anyone willing to throw an experimental patchset at some
> (recoverable!) hardware, please test it out and tell me any issues you
> encounter!
>
> Link on the issue tracker: https://issues.guix.gnu.org/72457
Just to let you know that I flagged this patch set a while ago already:
I think this is much needed and looks like a step in the right
direction, but I just haven’t allocated time to review it yet.
Apologies!
Could someone from the embedded or core teams (Cc’d) give a hand?
Thanks,
Ludo’.
next prev parent reply other threads:[~2024-08-12 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 4:09 Call for testers for bootloader subsystem rewrite! Lilah Tascheter
2024-08-12 14:28 ` Ludovic Courtès [this message]
2024-08-12 15:17 ` Efraim Flashner
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=87mslhbytc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dev@jpoiret.xyz \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=guix@cbaines.net \
--cc=lilah@lunabee.space \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=vagrant@debian.org \
--cc=zimon.toutoune@gmail.com \
/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).