From: Andreas Enge <andreas@enge.fr>
To: 65391-done@debbugs.gnu.org
Subject: bug#65391: Close
Date: Wed, 14 Feb 2024 10:13:32 +0100 [thread overview]
Message-ID: <ZcyEPIwweV0TPUJH@jurong> (raw)
In-Reply-To: <295ef8c8-574a-4169-98f3-6d9aaeb773f1@telenet.be>
After reading through the first tenth of what seems to be an interesting
discussion and skimming through the remainder, I take the liberty to close
this bug. Such a discussion had better take place on guix-devel; the report
itself does not start with an actionable proposal: "People need to..."
looks more like an infinite task to me that cannot be closed as finished
if taken literally.
I understand that certain concrete proposals coming from the discussion
have been filed as separate issues, and would suggest that people
interested in the topic continue to do so.
Andreas
prev parent reply other threads:[~2024-02-14 9:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 23:53 bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that Maxime Devos
2023-08-22 23:45 ` Csepp
2023-08-24 9:57 ` Simon Tournier
2023-08-24 17:23 ` Csepp
2023-08-24 14:52 ` Maxime Devos
2023-08-24 17:27 ` Csepp
2023-08-29 22:52 ` Maxime Devos
2023-08-30 2:36 ` Maxim Cournoyer
2023-08-24 15:02 ` Maxime Devos
2023-08-24 17:38 ` Csepp
[not found] ` <871qfpxp76.fsf@envs.net>
2023-08-27 3:38 ` Maxim Cournoyer
2023-08-27 8:16 ` bug#65391: [Cuirass] feature requests for dashboard 宋文武 via Bug reports for GNU Guix
2023-08-27 4:30 ` bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that Bruno Victal
2023-08-27 16:24 ` bug#65391: People need to report failing builds even Andy Tai
[not found] ` <handler.65391.B.169248925726403.ack@debbugs.gnu.org>
2023-08-29 14:03 ` bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that) Maxime Devos
2023-08-29 14:45 ` Maxim Cournoyer
2023-08-29 22:44 ` Maxime Devos
2023-08-30 2:28 ` Maxim Cournoyer
2023-08-30 10:39 ` Dr. Arne Babenhauserheide
2023-08-30 19:12 ` Maxim Cournoyer
2023-09-07 11:53 ` Simon Tournier
2023-09-11 8:30 ` Dr. Arne Babenhauserheide
2023-09-11 14:00 ` Simon Tournier
2023-09-11 23:12 ` Dr. Arne Babenhauserheide
2023-09-12 0:39 ` Simon Tournier
2023-08-30 11:50 ` Maxime Devos
2023-09-07 11:32 ` Simon Tournier
2023-09-11 7:28 ` bug#65391: People need to report failing builds even though we have ci.guix.gnu.org for that Csepp
2023-09-11 7:58 ` Simon Tournier
2023-09-11 21:52 ` Csepp
2023-09-12 18:43 ` bug#65391: Acknowledgement (People need to report failing builds even though we have ci.guix.gnu.org for that) Maxime Devos
2023-08-30 10:29 ` 宋文武 via Bug reports for GNU Guix
2024-02-14 9:13 ` Andreas Enge [this message]
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=ZcyEPIwweV0TPUJH@jurong \
--to=andreas@enge.fr \
--cc=65391-done@debbugs.gnu.org \
/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).