From: Christopher Baines <mail@cbaines.net>
To: "jgart" <jgart@dismail.de>
Cc: 71857@debbugs.gnu.org, ashish.is@lostca.se
Subject: [bug#71857] [PATCH] gnu: sbcl: Update to 2.4.6.
Date: Tue, 09 Jul 2024 12:10:33 +0200 [thread overview]
Message-ID: <87r0c298py.fsf@cbaines.net> (raw)
In-Reply-To: <f5fed1b4a0997ec5eca495d871ed83a739bb4202@dismail.de> (jgart@dismail.de's message of "Sun, 30 Jun 2024 21:15:47 +0000")
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
"jgart" <jgart@dismail.de> writes:
> Nice! Thanks for the contribution.
>
> I'll let Guillaume review this since I have limited CPU resources on my machine to build everything that depends on sbcl and QA is currently in an unknown state.
>
> Hi Christopher,
>
> Do you have any suggestions for what to do when QA is in an unknown state?
In this case, QA might eventually get around to processing this change,
but it's probably not going to build things since there are quite a few
dependent packages.
What you can do though is retitle the issue to indicate that this'll
need to go to a topic branch (e.g. lisp-team). To do that you'd send
something like the following to control@debbugs.gnu.org:
retitle 71857 [lisp-team] gnu: sbcl: Update to 2.4.6.
thanks
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2024-07-09 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 15:57 [bug#71857] [PATCH] gnu: sbcl: Update to 2.4.6 ashish.is--- via Guix-patches via
2024-06-30 21:15 ` jgart via Guix-patches via
2024-07-09 10:10 ` Christopher Baines [this message]
2024-07-29 8:35 ` [bug#71857] [PATCH lisp-team v2] gnu: sbcl: Update to 2.4.7 Ashish SHUKLA via Guix-patches via
2024-08-22 8:01 ` bug#71857: " Guillaume Le Vaillant
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=87r0c298py.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=71857@debbugs.gnu.org \
--cc=ashish.is@lostca.se \
--cc=jgart@dismail.de \
/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).