rlog(1) CLIX rlog(1)
NAME
rlog - Displays log messages and other information about RCS files
SYNOPSIS
rlog [flag ... ] file ...
FLAGS
-L Ignores RCS files that have no locks set. This flag is
convenient when combined with the -R, -h, or -l flags.
-R Displays only the RCS filename. This flag is convenient
for translating a working filename into an RCS filename.
-h Displays only the RCS filename, working filename, head,
default branch, access list, locks, symbolic names, and
suffix.
-t Displays the same as -h, plus the descriptive text.
-b Displays information about the revisions on the default
branch (normally the highest branch on the trunk).
-ddates Displays information about revisions with a check-in
date/time in the ranges given by the semicolon-separated
list of dates. A range with the form date1<date2 or
date2>date1 selects the revisions deposited between date1
and date2 (inclusive). A range with the form <date or
date> selects all revisions dated date or earlier. A range
with the form date< or >date selects all revisions dated
date or later. A range with the form date selects the
single, latest revision dated date or earlier. The
date/time strings date, date1, and date2 are in the free
format explained in co(1). Quoting is normally necessary,
especially for < and >. Note that the separator is a
semicolon.
-l[lockers] Displays information about locked revisions. If the
comma-separated list lockers of login names is given, only
the revisions locked by the given login names are
displayed. If the list is omitted, all locked revisions
are displayed.
-rrevisions Displays information about revisions given in the comma-
separated list revisions of revisions and ranges. A range
rev1:rev2 indicates revisions rev1 to rev2 on the same
branch; :rev indicates revisions from the beginning of the
branch up to and including rev; and rev: indicates
revisions starting with rev to the end of the branch
2/94 - Intergraph Corporation 1
rlog(1) CLIX rlog(1)
containing rev. An argument that is a branch indicates all
revisions on that branch. A range of branches indicates
all revisions on the branches in that range.
-sstates Displays information about revisions that have state
attributes that match one of the states given in the
comma-separated list states.
-w[logins] Displays information about revisions checked in by users
with login names appearing in the comma-separated list
logins. If logins is omitted, the user is assumed.
-Vn Emulates RCS version n, where n may be 3, 4, or 5. This
may be useful when interchanging RCS files with others who
are running older versions of RCS. To see which version of
RCS others are running, have them use the rlog command on
an RCS file; if none of the first few lines of output
contain the string branch: it is version 3; if the dates'
years have just two digits, it is version 4; otherwise, it
is version 5. An RCS file generated while emulating
version 3 will lose its default branch. An RCS revision
generated while emulating version 4 or earlier will have a
timestamp that is off by up to 13 hours. A revision
extracted while emulating version 4 or earlier will contain
dates of the form yy/mm/dd instead of yyyy/mm/dd and may
also contain different white space in the substitution for
$Log$.
-x suffixes Uses suffixes to characterize RCS files. A non-empty
suffix matches any pathname ending in the suffix. An empty
suffix matches any pathname of the form RCS/file or
path/RCS/file. The -x flag can specify a list of suffixes
separated by a slash (/). For example, -x,v/ specifies two
suffixes: ,v and the empty suffix. If two or more
suffixes are specified, they are tried in order when
looking for a RCS file; the first one that works is used
for that file. If no RCS file is found but an RCS file can
be created, the suffixes are tried in order to determine
the new RCS file's name. The default for suffixes is
installation-dependent; normally it is ,v/ for hosts like
UNIX that permit commas in file names, and is empty (the
empty suffix) for other hosts.
DESCRIPTION
The rlog command displays information about Revision Control System (RCS)
files.
Pathnames matching an RCS suffix denote RCS files; all others denote
working files. Names are paired as explained in ci(1).
2 Intergraph Corporation - 2/94
rlog(1) CLIX rlog(1)
The rlog command displays the following information for each RCS file: RCS
filename, working filename, head (that is, the number of the latest
revision on the trunk), default branch, access list, locks, symbolic
names, suffix, total number of revisions, number of revisions selected for
displaying, and descriptive text. This is followed by entries for the
selected revisions in reverse chronological order for each branch. For
each revision, rlog displays revision number, author, date/time, state,
number of lines added/deleted (with respect to the previous revision),
locker of the revision (if any), and log message. Without any specified
flags, rlog displays complete information. The flags restrict this
output.
The rlog command displays the intersection of the revisions selected with
the -d, -l, -s, and -w flags, intersected with the union of the revisions
selected by the -b and -r flags.
EXAMPLES
1. This example displays the names of all RCS files that have locks in
the subdirectory RCS.
rlog -L -R RCS/*,v
2. This example displays the headers of all the files that have locks in
the subdirectory RCS.
rlog -L -h RCS/*,v
3. This example displays the headers of all the files that have locks in
the subdirectory RCS plus the log messages of the locked revisions.
rlog -L -l RCS/*,v
4. This example displays complete information of all the files in the
subdirectory RCS.
rlog RCS/*,v
5. This example displays the headers of all files in the RCS directory,
plus the log information for revisions checked in by the login user
between January 1, 1990 and July 1, 1990.
rlog -wuser -d"> 1-Jan-1990 < 1-July-1990" RCS/*,v
NOTES
2/94 - Intergraph Corporation 3
rlog(1) CLIX rlog(1)
The separator for revision ranges in the -r flag used to be a dash (-)
instead of a colon (:), but this leads to confusion when symbolic names
contain a dash. For backwards compatibility, rlog -r still supports the
old dash separator, but it warns about this obsolete use.
EXIT VALUES
The exit value always refers to the last RCS file operated on and is 0 if
the operation was successful. If unsuccessful, this command exits with a
value of 1.
RELATED INFORMATION
Commands: ci(1), co(1), ident(1), rcs(1), rcsclean(1), rcsdiff(1),
rcsmerge(1), sccstorcs(1)
Files: rcsfile(4)
Walter F. Tichy, ``Design, Implementation, and Evaluation of a Revision
Control System,'' in Proceedings of the 6th International Conference on
Software Engineering, IEEE, Tokyo, Sept. 1982
Walter F. Tichy, ``RCS--A System for Version Control,'' Software--
Practice & Experience, 15, 7 (July 1985), pp. 637-654.
4 Intergraph Corporation - 2/94