GNU Info

Info Node: (pcl-cvs)Bugs

(pcl-cvs)Bugs


Next: Function and Variable Index Prev: Customization Up: Top
Enter node , (file) or (file)node

Bugs (known and unknown)
************************

   If you find a bug or misfeature, don't hesitate to tell us!  Send
email to <bug-gnu-emacs@gnu.org> which is gatewayed to the newsgroup
`gnu.emacs.bugs'.  Feature requests should also be sent there.  We
prefer discussing one thing at a time.  If you find several unrelated
bugs, please report them separately.  If you are running PCL-CVS under
XEmacs, you should also send a copy of bug reports to
<xemacs-beta@xemacs.org>.

   If you have problems using PCL-CVS or other questions, send them to
<help-gnu-emacs@gnu.org>, which is gatewayed to the `gnu.emacs.help'
newsgroup.  This is a good place to get help, as is <cvs-info@gnu.org>,
gatewayed to `gnu.cvs.help'.

   If you have ideas for improvements, or if you have written some
extensions to this package, we would like to hear from you.  We hope
that you find this package useful!

   Below is a partial list of currently known problems with PCL-CVS
version 2.0.

Unexpected output from CVS
     Unexpected output from CVS may confuse PCL-CVS.  It will create
     warning messages in the `*cvs*' buffer alerting you to any parse
     errors.  If you get these messages, please send a bug report to
     the email addresses listed above.  Include the contents of the
     `*cvs*' buffer, the output of the CVS process (which should be
     found in the `*cvs-tmp*' buffer), and the versions of Emacs,
     PCL-CVS and CVS you are using.


automatically generated by info2www version 1.2.2.9