From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Efraim Flashner <efraim@flashner.co.il>, 64667@debbugs.gnu.org
Subject: [bug#64667] [PATCH 1/1] gnu: Add grub-coreboot
Date: Fri, 15 Sep 2023 16:31:59 +0200 [thread overview]
Message-ID: <20230915163159.51d2e7fa@primary_laptop> (raw)
In-Reply-To: <87il8xv4km.fsf@wireframe>
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
Hi,
On Tue, 29 Aug 2023 15:58:33 -0700
Vagrant Cascadian <vagrant@debian.org> wrote:
> Still seems a bit brief, but I suppose it is not terrible. :)
With:
> I might want to identify in the comment which tests need a coreboot
> image and which need cbfstool for example.
and:
> Are all of the failures or skipped tests things that cannot reasonably
> be fixed, such as being unable to build a coreboot image or cbfstool?
I've looked and luckily all the tests that we need to disable fail
because they miss a Coreboot image.
I'll send a v2.
> If it is really involved, perhaps a link to a more detailed
> explanation, such as to a comment filed on this bug report.
In the v2 I've also improved a bit the description of the issue.
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-15 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 16:49 [bug#64668] [PATCH 0/1] Add grub-coreboot Denis 'GNUtoo' Carikli
2023-07-16 16:56 ` [bug#64667] [PATCH 1/1] gnu: " Denis 'GNUtoo' Carikli
2023-07-18 18:00 ` Vagrant Cascadian
2023-07-27 3:42 ` Denis 'GNUtoo' Carikli
2023-08-29 22:58 ` Vagrant Cascadian
2023-09-15 14:31 ` Denis 'GNUtoo' Carikli [this message]
2023-11-23 11:27 ` Denis 'GNUtoo' Carikli
2023-11-24 21:42 ` bug#64667: " Vagrant Cascadian
2023-09-15 14:34 ` [bug#64667] [PATCH v2] " Denis 'GNUtoo' Carikli
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=20230915163159.51d2e7fa@primary_laptop \
--to=gnutoo@cyberdimension.org \
--cc=64667@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=vagrant@debian.org \
/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.