From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Breakage due to b07581d6e24bf5fa4676bcebaba75315bbbb01e6
Date: Sat, 31 Jul 2021 18:59:45 +0200 [thread overview]
Message-ID: <874kca7726.fsf@elephly.net> (raw)
Hi Pierre,
looks like your commit to upgrade sbcl broke thousands of builds:
https://ci.guix.gnu.org/eval/69904?status=failed
I have two requests:
- Please revert the commit.
- Please push commits like this to a separate branch and have the
CI build the branch first. Only then merge.
Thanks,
--
Ricardo
next reply other threads:[~2021-07-31 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 16:59 Ricardo Wurmus [this message]
2021-07-31 17:01 ` Breakage due to b07581d6e24bf5fa4676bcebaba75315bbbb01e6 Ricardo Wurmus
2021-07-31 17:37 ` Pierre Neidhardt
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=874kca7726.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/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).