From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: suggestion: add link to Emacs manual node `Bugs' in report-emacs-bug instructions
Date: Tue, 7 Oct 2008 12:50:26 -0700 [thread overview]
Message-ID: <000501c928b5$f21ae410$0200a8c0@us.oracle.com> (raw)
Seems like we are forever repeating the excellent instructions found in the
Emacs manual node `Bugs' (and subnodes) to users in help-gnu-emacs. How about
including a link to that node in the `*mail*' buffer's instructions for
`report-emacs-bug'?
That is, instead of just saying "Please describe exactly what actions triggered
the bug and the precise symptoms of the bug", we give them a link to the manual
so they can see just what is recommended for such a description. Many users
could use some guidelines about what kinds of information are most helpful and
just what is meant by "precise symptoms".
next reply other threads:[~2008-10-07 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 19:50 Drew Adams [this message]
2008-10-07 20:00 ` suggestion: add link to Emacs manual node `Bugs' in report-emacs-bug instructions Chong Yidong
2008-10-07 20:06 ` Drew Adams
2008-10-07 20:23 ` Lennart Borgman (gmail)
2008-10-07 20:36 ` Drew Adams
2008-10-07 20:48 ` Stefan Monnier
2008-10-10 18:37 ` Reiner Steib
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='000501c928b5$f21ae410$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=emacs-devel@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/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).