This manual page is part of Xcode Tools version 3.2

To obtain these tools:

If you are running a version of Xcode Tools other than 3.2, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • For more information about the manual page format, see the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Reference Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.


RCS2LOG(1)                               BSD General Commands Manual                              RCS2LOG(1)

NAME
     rcs2log -- RCS to ChangeLog generator

SYNOPSIS
     rcs2log [-c changelog] [-h hostname] [-i indent] [-l length] [-R] [-r option] [-t tabwidth]
             [-u login<TAB>fullname<TAB>mailaddr] [-v] [--help] [--version] [file ...]

DESCRIPTION
     The rcs2log utility generates a change log prefix from RCS files (perhaps in the CVS repository) and
     the ChangeLog (if any).

     The options are as follows:

     -c changelog
             Output a change log prefix to changelog (default ChangeLog).

     -h hostname
             Use hostname in change log entries (default current host).

     -i indent
             Indent change log lines by indent spaces (default 8).

     -l length
             Try to limit log lines to length characters (default 79).

     -R      If no file(s) are given and RCS is used, recurse through working directory.

     -r option
             Pass option to subsidiary log command.

     -t tabwidth
             Tab stops are every tabwidth characters (default 8).

     -u login<TAB>fullname<TAB>mailaddr
             Assume login has fullname and mailaddr.

     -v      Append RCS revision to file names in log lines.

     --help  Output help.

     --version
             Output version number.

SEE ALSO
     rcs(1), rcsintro(1), rlog(1), rcsfile(5)

AUTHORS
     Paul Eggert <[email protected]>

BUGS
     Report bugs to <[email protected]>.

BSD                                           February 15, 2003                                          BSD

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.