From: Adam Porter <adam@alphapapa.net>
To: 39983@debbugs.gnu.org
Subject: bug#39983: Acknowledgement (help)
Date: Sun, 8 Mar 2020 08:22:42 -0500 [thread overview]
Message-ID: <CAO_b3FWejUJSkx6rAHuBY2_OA==WD5=9pb9dAVA40vixf2FyPA@mail.gmail.com> (raw)
In-Reply-To: <handler.39983.B.15836735531790.ack@debbugs.gnu.org>
Okay, here's what happened:
1. I found a bug in Guix that I wanted to report.
2. I checked the manual, which directed me to https://issues.guix.gnu.org/.
3. That page directed me to "submit your patches or email
bug-guix@gnu.org to open a new issue." There were no further
instructions, so I guessed that sending an email with the body "help"
would return one with instructions on how to file an actual bug
report.
4. Instead, that filed a bug reporting "help."
Perhaps this bug could be repurposed into one about improving the
instructions for reporting bugs. :) Now I'll file the real bug
report...
On 3/8/20, GNU bug Tracking System <help-debbugs@gnu.org> wrote:
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> bug-guix@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 39983@debbugs.gnu.org.
>
> Please do not send mail to help-debbugs@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 39983: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=39983
> GNU Bug Tracking System
> Contact help-debbugs@gnu.org with problems
>
next prev parent reply other threads:[~2020-03-08 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 13:19 bug#39983: help Adam Porter
[not found] ` <handler.39983.B.15836735531790.ack@debbugs.gnu.org>
2020-03-08 13:22 ` Adam Porter [this message]
2020-03-11 19:00 ` bug#39983: Acknowledgement (help) Leo Famulari
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='CAO_b3FWejUJSkx6rAHuBY2_OA==WD5=9pb9dAVA40vixf2FyPA@mail.gmail.com' \
--to=adam@alphapapa.net \
--cc=39983@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).