From: Andreas Enge <andreas@enge.fr>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "John Kehayias" <john.kehayias@protonmail.com>,
73765@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#73765] Request for merging "meson-enable-parallel-tests" branch
Date: Thu, 28 Nov 2024 09:51:54 +0100 [thread overview]
Message-ID: <Z0gvKluNncrJF9vv@jurong> (raw)
In-Reply-To: <878qt3kdhc.fsf@gmail.com>
Am Thu, Nov 28, 2024 at 04:46:07PM +0900 schrieb Maxim Cournoyer:
> I had set up the build job on CI for x86-64 only in my original
> configuration and had forgotten about it -- it's only been enabled for
> other archs recently.
Me too - it had been built out for x86_64, and I had forgotten about i686.
For aarch64, I think we do not have the build power at ci to wait for it,
and QA is unfortunately almost not working right now.
> > PS: Andreas I saw some messages earlier in this thread that again didn't
> > go to others. Annoyingly, the debbugs bug number address doesn't go to
> > anyone (that I know of) and I've frequently missed or miss-sent messages
> > because of that. Just thought I'd let you know in case you missed
> > that.
> That's an annoyance of Debbugs yes. I wish it'd handle CCing all
> participants itself when any message reaches a bug they are
> participating in.
Is this true? I think I usually get messages directed at bugs I have opened
or participated in. Or is it just when people cc me explicitly? So are you
saying that when sending mail to a bug, one should manually add all
participants in cc? This would be a lot of work - since issues.guix.gnu.org
does not show email addresses, one would need to download the raw message,
or look at debbugs.gnu.org and type the addresses by hand.
Andreas
next prev parent reply other threads:[~2024-11-28 8:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 5:36 [bug#73765] Request for merging "meson-enable-parallel-tests" branch Maxim Cournoyer
2024-10-15 9:26 ` Christopher Baines
2024-10-29 0:19 ` Maxim Cournoyer
2024-11-22 12:59 ` [bug#73765] Rebased Andreas Enge
2024-11-22 14:45 ` [bug#73765] Request for merging "meson-enable-parallel-tests" branch Ludovic Courtès
2024-11-22 15:03 ` Andreas Enge
2024-11-22 15:27 ` Andreas Enge
2024-11-25 8:39 ` [bug#73765] Results Andreas Enge
2024-11-26 17:10 ` [bug#73765] Request for merging "meson-enable-parallel-tests" branch Ludovic Courtès
2024-11-27 11:51 ` bug#73765: " Andreas Enge
2024-11-28 6:27 ` [bug#73765] " Maxim Cournoyer
2024-11-28 5:43 ` John Kehayias via Guix-patches via
2024-11-28 7:46 ` Maxim Cournoyer
2024-11-28 8:51 ` Andreas Enge [this message]
2024-11-28 15:37 ` John Kehayias via Guix-patches via
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=Z0gvKluNncrJF9vv@jurong \
--to=andreas@enge.fr \
--cc=73765@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=ludo@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).