From: Christopher Baines <mail@cbaines.net>
To: "Sören Tempel" <soeren@soeren-tempel.net>
Cc: 65486@debbugs.gnu.org
Subject: [bug#65486] [PATCH] syscalls: Add support for musl libc
Date: Tue, 10 Oct 2023 18:15:27 +0100 [thread overview]
Message-ID: <87a5sqflcy.fsf@cbaines.net> (raw)
In-Reply-To: <2Q84POXRPGUHK.2VMS1AUMSNS7X@8pit.net>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Sören Tempel <soeren@soeren-tempel.net> writes:
> Hi,
>
> Ludovic Courtès <ludo@gnu.org> wrote:
>> To do that, can you resend both syscalls.scm patch (with ‘git
>> send-email’) here? Then we’ll check qa.guix to ensure it builds things.
>
> Did I resend the patches correctly? I noticed that the QA status is
> still unknown on issues.guix.gnu.org. Is it required to open a new
> thread instead of replying to the existing one?
The unknown status is because QA doesn't have any information on the
builds. Currently there's a limit of 300 builds per system for patches
which these changes exceed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2023-10-10 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 6:33 [bug#65486] [PATCH] syscalls: Add support for musl libc soeren
2023-09-09 13:04 ` [bug#65486] [PATCH v2] " soeren
2023-09-11 21:09 ` [bug#65486] [PATCH] " Ludovic Courtès
2023-09-13 10:23 ` Sören Tempel
2023-09-13 20:39 ` Ludovic Courtès
2023-09-15 10:57 ` Sören Tempel
2023-09-17 10:14 ` bug#65486: " Ludovic Courtès
2023-09-17 10:17 ` [bug#65486] " Ludovic Courtès
2023-09-17 11:38 ` Christopher Baines
2023-09-17 15:21 ` [bug#65486] [PATCH v3] syscalls: Consistently use existing linux? definition soeren
2023-09-17 15:21 ` [bug#65486] [PATCH v3] syscalls: Add support for musl libc soeren
2023-09-30 10:16 ` [bug#65486] [PATCH] " Sören Tempel
2023-10-10 17:15 ` Christopher Baines [this message]
2023-10-23 10:11 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5sqflcy.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=65486@debbugs.gnu.org \
--cc=soeren@soeren-tempel.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.