view BUGS @ 47211:3a7c7e0c12f7

(cvs-run-process): Use a pty rather than a pipe to work around the cvs/ssh/libc bug. (cvs-update-header): Understand `cvs admin -m<rev>:<msg>' syntax. (defun-cvs-mode): Use the new `declare' thingy. (cvs-edit-log-text-at-point, cvs-mode-edit-log, cvs-do-edit-log) (cvs-edit-log-minor-wrap, cvs-edit-log-filelist): New funs. (cvs-mode-undo): Use `cvs add' for (CONFLICT. REMOVED).

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 P in Emacs) to
make sure it isn't a known issue.