annotate BUGS @ 72009:e7287a023d2c

Merge from gnus--rel--5.10 Patches applied: * gnus--rel--5.10 (patch 116-117) - Update from CVS 2006-07-18 Andreas Seltenreich <[e-mail]> [ Backported bug fixes from No Gnus. ] * lisp/gnus/nnweb.el (nnweb-google-parse-1): Update regexp for author and date. (nnweb-google-search): Respect nnweb-max-hits as upper bound. (nnweb-request-article): Do proper xwfu encoding when fetching articles by message-id. * lisp/gnus/gnus-srvr.el (gnus-browse-unsubscribe-group): Don't subscribe unsubscribed groups as if they were killed ones. It causes duplicate entries in gnus-newsrc-alist. 2006-07-17 Reiner Steib <[e-mail]> * lisp/gnus/gnus-sum.el (gnus-summary-delete-article): Don't use TAB in doc string. Revision: [e-mail]/emacs--devo--0--patch-357

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.