From: Glenn Morris <rgm@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 41373@debbugs.gnu.org
Subject: bug#41373: GNU ELPA: Add "reporting bugs" to individual package pages
Date: Mon, 18 May 2020 14:04:45 -0400 [thread overview]
Message-ID: <62r1vh6rwi.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CADwFkmkVLtBN_R6Z+0WdKjwsBYUHgXAFpjfiR17atG+BUq5zRQ@mail.gmail.com> (Stefan Kangas's message of "Sun, 17 May 2020 19:14:57 -0700")
Stefan Kangas wrote:
> I think this is situation could be alleviated by including a static
> section on the pages for individual packages which explains how to
> report bugs.
This will vary from package to package. I doubt "M-x report-emacs-bug"
is right in anything more than a small minority of cases (because it
would require the package developer to subscribe to bug-gnu-emacs).
I would think that the package itself needs to contain its bug reporting
information, independent of elpa.gnu.org.
next prev parent reply other threads:[~2020-05-18 18:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 2:14 bug#41373: GNU ELPA: Add "reporting bugs" to individual package pages Stefan Kangas
2020-05-18 18:04 ` Glenn Morris [this message]
2020-05-18 18:07 ` Eli Zaretskii
2020-05-19 0:20 ` Stefan Kangas
2020-05-18 18:12 ` Dmitry Gutov
2020-05-19 0:15 ` Stefan Kangas
2020-05-20 3:54 ` Richard Stallman
2020-05-20 5:30 ` Eric Abrahamsen
2020-05-25 9:04 ` Bastien
2020-05-25 15:39 ` Eric Abrahamsen
2020-05-25 17:09 ` Glenn Morris
2020-05-25 17:49 ` Eric Abrahamsen
2020-06-01 6:32 ` Bastien
2020-06-01 18:29 ` Eric Abrahamsen
2020-06-01 18:41 ` Eli Zaretskii
2020-06-01 19:25 ` Eric Abrahamsen
2020-06-01 19:38 ` Eli Zaretskii
2020-06-01 20:06 ` Eric Abrahamsen
2020-06-01 19:52 ` Glenn Morris
2020-06-01 20:31 ` Eric Abrahamsen
2020-05-25 11:51 ` Dmitry Gutov
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62r1vh6rwi.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=41373@debbugs.gnu.org \
--cc=stefankangas@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/emacs.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).