Mercurial > emacs

comparison man/trouble.texi @ 26021:4f5e4ec69f6a

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Add emacs-prestest-bug@gnu.org analogous to bug-gnu-emacs@gnu.org.
author Gerd Moellmann <gerd@gnu.org>
date Thu, 14 Oct 1999 12:12:30 +0000
parents ac7e9e5e2ccb
children 75463d908406
comparison
equal deleted inserted replaced
26020:f700437bf330 26021:4f5e4ec69f6a
460 @node Checklist 460 @node Checklist
461 @subsection Checklist for Bug Reports 461 @subsection Checklist for Bug Reports
462 462
463 @cindex reporting bugs 463 @cindex reporting bugs
464 The best way to send a bug report is to mail it electronically to the 464 The best way to send a bug report is to mail it electronically to the
465 Emacs maintainers at @samp{bug-gnu-emacs@@gnu.org}. (If you 465 Emacs maintainers at @samp{bug-gnu-emacs@@gnu.org}, or to
466 want to suggest a change as an improvement, use the same address.) 466 @samp{emacs-pretest-bug@@gnu.org} if you are pretesting an Emacs beta
467 release. (If you want to suggest a change as an improvement, use the
468 same address.)
467 469
468 If you'd like to read the bug reports, you can find them on the 470 If you'd like to read the bug reports, you can find them on the
469 newsgroup @samp{gnu.emacs.bug}; keep in mind, however, that as a 471 newsgroup @samp{gnu.emacs.bug}; keep in mind, however, that as a
470 spectator you should not criticize anything about what you see there. 472 spectator you should not criticize anything about what you see there.
471 The purpose of bug reports is to give information to the Emacs 473 The purpose of bug reports is to give information to the Emacs