From: Ricardo Wurmus <rekado@elephly.net>
To: Leo Famulari <leo@famulari.name>
Cc: 42686@debbugs.gnu.org
Subject: [bug#42686] Update to linux-libre 5.7
Date: Tue, 04 Aug 2020 12:04:56 +0200 [thread overview]
Message-ID: <87o8nqg20n.fsf@elephly.net> (raw)
In-Reply-To: <20200803215529.GA16925@jasmine.lan>
Leo Famulari <leo@famulari.name> writes:
> On Mon, Aug 03, 2020 at 11:00:32PM +0200, Ricardo Wurmus wrote:
>>
>> Leo Famulari <leo@famulari.name> writes:
>>
>> > I'd like to push this as a "kernel-updates" branch and let Cuirass build
>> > it. In the past, we always did this so that nobody had to build it
>> > themselves. CI admins, can we do this?
>>
>> Sure! Those with a valid client certificate can visit
>>
>> https://ci.guix.gnu.org/admin/specifications
>>
>> and add “kernel-updates” to the specifications.
>
> Cool! I don't have a certificate or know who does.
I do! I just added “kernel-updates” to the specifications.
> Will somebody do this? Or should I create one for myself? If so, can you
> give me some details about how to do that?
All people with an account on ci.guix.gnu.org should be able to generate
a client certificate for themselves. Documentation and scripts are in
the /root/maintenance directory.
--
Ricardo
next prev parent reply other threads:[~2020-08-04 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 22:43 [bug#42686] Update to linux-libre 5.7 Leo Famulari
2020-08-03 8:08 ` Mathieu Othacehe
2020-08-03 17:42 ` Leo Famulari
2020-08-03 21:00 ` Ricardo Wurmus
2020-08-03 21:55 ` Leo Famulari
2020-08-04 10:04 ` Ricardo Wurmus [this message]
2020-08-05 17:25 ` Leo Famulari
2020-08-04 10:36 ` Danny Milosavljevic
2020-08-05 17:24 ` Leo Famulari
2020-08-05 17:27 ` bug#42686: " Leo Famulari
2020-08-06 7:35 ` [bug#42686] " Mathieu Othacehe
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=87o8nqg20n.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=42686@debbugs.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).