From: Mathieu Othacehe <othacehe@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 55024-done@debbugs.gnu.org
Subject: bug#55024: [cuirass] '+' character in branch name causes problems
Date: Tue, 26 Apr 2022 10:21:26 +0200 [thread overview]
Message-ID: <87czh4w8zd.fsf@gnu.org> (raw)
In-Reply-To: <87fsm9w521.fsf@gmail.com> (Maxim Cournoyer's message of "Tue, 19 Apr 2022 09:55:50 -0400")
Hello,
> https://ci.guix.gnu.org/jobset/wip-ipython%2Bpolyglossia.
Fixed in Cuirass with 1c45ae3c6b7ed9d99b2a1f61d707b40e68c2f7a4. The
commit is not yet deployed on Berlin but I took care of disabling the
wip-ipython%2Bpolyglossia specification in the database.
Thanks,
Mathieu
next prev parent reply other threads:[~2022-04-26 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 13:55 bug#55024: [cuirass] '+' character in branch name causes problems Maxim Cournoyer
2022-04-26 8:21 ` Mathieu Othacehe [this message]
2022-04-27 3:04 ` 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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czh4w8zd.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=55024-done@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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).