From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Douglas Linford <drkrider@gmail.com>
Cc: "44257-done@debbugs.gnu.org" <44257@debbugs.gnu.org>
Subject: bug#44257: guix boot stop
Date: Wed, 28 Oct 2020 18:11:29 +0100 [thread overview]
Message-ID: <87361yz35q.fsf@nckx> (raw)
In-Reply-To: <296E87C0-08A8-405A-973A-A0B00140C158@getmailspring.com>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Douglas,
To augment Leo's answer, here's the full skinny:
<https://debbugs.gnu.org/server-control.html>.
Douglas Linford 写道：
> Is there a more appropriate place to post issues so as not to
> fill up the bug reports with needless issues?
In our system, ‘issues’ are synonymous with ‘bugs’ (‘shortcomings
in the software’, which can include feature requests). But
opening a bug that turns out not to be one isn't the end of the
world! They are easiest to fix...
Questions or other ‘troubles’ that aren't (yet) obvious flaws are
always welcome at help-guix@gnu.org. For more technical design-
and code-related discussions there's guix-devel@gnu.org.
Oy vey, semantics,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-10-28 17:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 14:23 bug#44257: guix boot stop Douglas Linford
2020-10-27 16:25 ` Julien Lepiller
2020-10-27 18:13 ` Douglas Linford
2020-10-28 14:21 ` Ludovic Courtès
2020-10-28 14:55 ` Douglas Linford
2020-10-28 16:24 ` Leo Famulari
2020-10-28 16:32 ` Douglas Linford
2020-10-28 16:45 ` Leo Famulari
2020-10-28 17:31 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-10-28 18:00 ` Leo Famulari
2020-10-28 18:28 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-10-28 16:33 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-10-28 16:45 ` Douglas Linford
2020-10-28 17:11 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-10-28 17:43 ` Julien Lepiller
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=87361yz35q.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=44257@debbugs.gnu.org \
--cc=drkrider@gmail.com \
--cc=me@tobias.gr \
/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.