unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 60373@debbugs.gnu.org
Subject: [bug#60373] Kernel job for Cuirass
Date: Tue, 27 Dec 2022 21:22:48 -0500	[thread overview]
Message-ID: <Y6uoeHOZoTGBVjCG@jasmine.lan> (raw)

[-- Attachment #1: Type: text/plain, Size: 443 bytes --]

Here are some patches to create a 'kernel-updates' Cuirass
specification, so that CI will build kernel-related things based on
changes to a kernel-updates Git branch.

The first patch creates a manifest of packages named "linux-libre-*" for
the Guix source tree, and the second patch creates the Cuirass spec for
maintenance.git.

I can test the manifest with `guix weather`, but I'm not sure how to
test the Cuirass spec.

Advice is welcome!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2022-12-28  2:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28  2:22 Leo Famulari [this message]
2022-12-28  2:25 ` [bug#60373] [PATCH] maint: Add a manifest for everything related to linux-libre Leo Famulari
2022-12-28  2:29 ` [bug#60373] [PATCH] hydra: cuirass: Add 'kernel-updates' jobset Leo Famulari
2022-12-28 14:35   ` [bug#60373] Kernel job for Cuirass Mathieu Othacehe
2022-12-28 22:50     ` Leo Famulari
2022-12-29 10:33       ` Mathieu Othacehe
2022-12-29 18:54         ` Leo Famulari
2023-01-05  3:48         ` Leo Famulari
2023-01-05 17:37           ` Mathieu Othacehe
2023-01-06  1:19             ` Leo Famulari
2023-01-06  3:00               ` Leo Famulari
2023-01-06  5:33                 ` Leo Famulari
2023-01-06  6:27                   ` Leo Famulari
2023-01-07 14:50                   ` Mathieu Othacehe
2023-01-07 14:47                 ` Mathieu Othacehe
2023-01-07 18:38                   ` Leo Famulari
2022-12-28 22:54 ` [bug#60373] [PATCH v2] maint: Add a manifest for everything related to linux-libre 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

  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=Y6uoeHOZoTGBVjCG@jasmine.lan \
    --to=leo@famulari.name \
    --cc=60373@debbugs.gnu.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 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).