rcs: Reporting bugs
3.4 Reporting bugs
==================
To report bugs or suggest enhancements for GNU RCS, please visit its
homepage (<http://www.gnu.org/software/rcs/>) to find directions on how
to “file a bug report” online, or send electronic mail to
<help-rcs@gnu.org>. (If you use the web interface, you don’t need to
also send email, since that is done automatically.)
For bug reports, please include enough information for the
maintainers to reproduce the problem. Generally speaking, that means:
• The RCS version, command(s) and manual section(s) involved.
• Hardware and operating system names and versions.
• The contents of any input files necessary to reproduce the bug.
• The expected behavior and/or output.
• A description of the problem and samples of any erroneous output.
• Options you gave to ‘configure’ other than specifying installation
directories.
• Anything else that you think would be helpful.
When in doubt whether something is needed or not, include it. It’s
better to include too much than to leave out something important.
Patches are welcome; if possible, please make them with ‘git
format-patch’ and include ‘ChangeLog’ entries (⇒(emacs)Change
Log). Please see file ‘HACKING’ in the repo, for coding standards.
Info Catalog
rcs: Still missing
rcs: Hacking