view BUGS @ 64780:4def766e2c3f

Revision: miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-515 Merge from gnus--rel--5.10 Patches applied: * gnus--rel--5.10 (patch 104) - Update from CVS 2005-08-05 Daiki Ueno <ueno@unixuser.org> * lisp/gnus/mml2015.el (mml2015-pgg-sign): Make sure micalg is correct. * lisp/gnus/pgg-parse.el (pgg-parse-hash-algorithm-alist): Add SHA-2. 2005-08-06 Romain Francoise <romain@orebokech.com> * lisp/gnus/message.el: Fix typo in docstring. 2005-07-16 Romain Francoise <romain@orebokech.com> * lisp/gnus/gnus-uu.el (gnus-uu-save-article): Use `message-make-date' instead of `current-time-string' as the latter creates a time string that is not RFC 2822 compliant (it lacks the zone).
author Miles Bader <miles@gnu.org>
date Sun, 07 Aug 2005 23:56:33 +0000
parents 8ce686bd7f4f
children fb8bf24d2eb9
line wrap: on
line source

If you think you may have found a bug in GNU Emacs, please
read the Bugs section of the Emacs manual for advice on
(1) how to tell when to report a bug, and
(2) how to write a useful bug report and what information
it needs to have.

There are three ways to read the Bugs section.

(1) In a printed copy of the Emacs manual.
You can order one from the Free Software Foundation;
see the file etc/ORDERS.  But if you don't have a copy on
hand and you think you have found a bug, you shouldn't wait
to get a printed manual; you should read the section right away
as described below.

(2) With Info.  Start Emacs, do C-h i to enter Info,
then m Emacs RET to get to the Emacs manual, then m Bugs RET
to get to the section on bugs.  Or use standalone Info in
a like manner.  (Standalone Info is part of the Texinfo distribution,
not part of the Emacs distribution.)

(3) By hand.  Do
    cat info/emacs* | more "+/^File: emacs,  Node: Bugs,"

Please first check the file etc/PROBLEMS (e.g. with C-h C-e in Emacs) to
make sure it isn't a known issue.