From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-devel@gnu.org
Cc: guix-devel@gnu.org
Subject: Re: Resurrecting top-notch continuous integration for Guile
Date: Mon, 06 Feb 2023 17:58:52 +0100 [thread overview]
Message-ID: <87zg9q20j7.fsf@inria.fr> (raw)
In-Reply-To: <87lell2qgc.fsf@inria.fr> ("Ludovic Courtès"'s message of "Sun, 29 Jan 2023 18:36:19 +0100")
Hi!
Ludovic Courtès <ludo@gnu.org> skribis:
> There’s still much tweaking we can do, but the basics are in place, and
> I find it pretty cool. :-) If there are no objections, I’ll merge this
> branch into “main”. It’s going to be nice to have a dashboard to look
> at before the next release!
Merged in Guile’s ‘main’ branch as commit
32f33756d0fbbf28e848f087375f75c265d0a46c!
If Guix is your thing, you can now get started hacking on Guile with:
guix shell
The continuous integration jobs are visible at:
https://ci.guix.gnu.org/jobset/guile
Happy hacking!
Ludo’.
next prev parent reply other threads:[~2023-02-06 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 17:36 Resurrecting top-notch continuous integration for Guile Ludovic Courtès
2023-01-29 18:34 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-01-29 21:02 ` Tobias Geerinckx-Rice
2023-02-06 16:58 ` Ludovic Courtès [this message]
2023-02-06 20:55 ` Maxim Cournoyer
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zg9q20j7.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=guix-devel@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.
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).