Next: admin, Previous: info, Up: Subcommands
ADDITIONAL OPTIONS: ‘-r’ (once or twice), ‘-l’
The changes subcommand helps you find what versions modify a specific file or files. For example, suppose you fixed a bug a long time ago and now it shows up again in the current version. You would like to know what project versions modify a certain file so you can find out who undid your bug-fix and blame them!
Like
prcs diff
, the options may specify zero, one, or two versions (using ‘-r’ options). Specifying no ‘-r’ options is equivalent to supplying the single option ‘-r.’, the version from which the current working directory was checked out. A ‘-r’ option that specifies only a major version (leaving off the minor version and its preceding period) implicitly has a minor version of@
. When one version specifier is given, only that version is scanned for changes. Two version specifiers cause a range of versions to be scanned. In the two version case, one version must be an ancestor of the other, and reversing the order of the two versions will reverse the order of the output.When file-or-dir arguments are present, they restrict the change report to the specified files or subdirectory trees. Otherwise all files are reported.
For each specified version that modifies a file (in the reporting set) relative to one of its parent versions,
changes
prints the project name, major and minor version identifiers, date and time checked in, and the user who checked in the version. Then it prints the parent version and a listing of all the selected files that were modified, including: addition, deletion, rename, type change, symlink change, or version change. For regular files,changes
also prints the number of lines added and removed by the modification. If a project version does not modify any of the selected files, nothing is printed.When the ‘-l’ option is present,
changes
also prints the version-log associated with each version.