From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Vagrant Cascadian <vagrant@debian.org>,
guix-devel <guix-devel@gnu.org>,
Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: linux-libre source tarballs
Date: Sun, 2 May 2021 18:38:54 -0400 [thread overview]
Message-ID: <YI8p/kgFHdG8/d4D@jasmine.lan> (raw)
In-Reply-To: <YI8nB0SVeggqHeS8@jasmine.lan>
On Sun, May 02, 2021 at 06:26:15PM -0400, Leo Famulari wrote:
> In the meantime, can we make a 'kernel-updates' Cuirass job again, that
> would build a kernel-updates branch on Savannah?
Mistake: I'd want to call the branch wip-kernel-updates, so that it's
rebaseable.
> We had one recently for a brief period but I stopped using it, because I
> could work more quickly building the tarballs "by hand" (although I've
> only been doing it for x86_64).
>
> However, it would be helpful to let Cuirass at least try to build these
> derivations, with me checking the results and retrying failures before
> pushing kernel-updates to master.
next prev parent reply other threads:[~2021-05-02 22:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 1:45 linux-libre source tarballs Vagrant Cascadian
2021-05-02 2:45 ` Leo Famulari
2021-05-02 4:42 ` Leo Famulari
2021-05-02 21:08 ` Ludovic Courtès
2021-05-02 22:26 ` Leo Famulari
2021-05-02 22:38 ` Leo Famulari [this message]
2021-05-03 15:44 ` linux-libre source tarballs (disable "deblob-check"?) Leo Famulari
2021-05-03 16:39 ` linux-libre source tarballs Alexandre Oliva
2021-05-03 17:13 ` Leo Famulari
2021-05-06 4:10 ` Alexandre Oliva
2021-05-06 21:23 ` Leo Famulari
2021-05-06 20:30 ` Maxim Cournoyer
2021-05-09 3:27 ` Alexandre Oliva
2021-05-30 4:50 ` Vagrant Cascadian
2021-05-31 3:42 ` Leo Famulari
2021-05-31 19:57 ` Mathieu Othacehe
2021-08-01 20:45 ` source tarballs potentially built for each derivation Vagrant Cascadian
2021-08-01 21:04 ` Vagrant Cascadian
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=YI8p/kgFHdG8/d4D@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=othacehe@gnu.org \
--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.