view BUGS @ 77114:b64b5f4be390

Merge from gnus--rel--5.10 Patches applied: * gnus--rel--5.10 (patch 214-215) - Merge from emacs--devo--0 - Update from CVS 2007-04-10 Katsumi Yamaoka <[e-mail]> * lisp/gnus/gnus-msg.el (gnus-inews-yank-articles): Use message-exchange-point-and-mark instead of exchange-point-and-mark. 2007-04-09 Katsumi Yamaoka <[e-mail]> * lisp/gnus/message.el (message-yank-original): Make sure cited text ends with newline; don't exchange point and mark. 2007-04-07 Chong Yidong <[e-mail]> * lisp/gnus/tls.el (open-tls-stream): Properly handle case where there is no associated buffer. Revision: [e-mail]/emacs--devo--0--patch-697

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.