1RLOG(1) General Commands Manual RLOG(1)
2
6 rlog - print log messages and other information about RCS files
7
9 rlog [ options ] file ...
10
12 rlog prints information about RCS files.
13 Pathnames matching an RCS suffix denote RCS files; all others denote
15 working files. Names are paired as explained in ci(1).
16 rlog prints the following information for each RCS file: RCS pathname,
18 working pathname, head (i.e., the number of the latest revision on the
19 trunk), default branch, access list, locks, symbolic names, suffix,
20 total number of revisions, number of revisions selected for printing,
21 and descriptive text. This is followed by entries for the selected
22 revisions in reverse chronological order for each branch. For each
23 revision, rlog prints revision number, author, date/time, state, number
24 of lines added/deleted (with respect to the previous revision), locker
25 of the revision (if any), and log message. All times are displayed in
26 Coordinated Universal Time (UTC) by default; this can be overridden
27 with -z. Without options, rlog prints complete information. The
28 options below restrict this output.
29 -L Ignore RCS files that have no locks set. This is convenient in
31 combination with -h, -l, and -R.
32 -R Print only the name of the RCS file. This is convenient for trans‐
34 lating a working pathname into an RCS pathname.
35 -h Print only the RCS pathname, working pathname, head, default
37 branch, access list, locks, symbolic names, and suffix.
38 -t Print the same as -h, plus the descriptive text.
40 -N Do not print the symbolic names.
42 -b Print information about the revisions on the default branch, nor‐
44 mally the highest branch on the trunk.
45 -ddates
47 Print information about revisions with a checkin date/time in the
48 ranges given by the semicolon-separated list of dates. A range of
49 the form d1<d2 or d2>d1 selects the revisions that were deposited
50 between d1 and d2 exclusive. A range of the form <d or d> selects
51 all revisions earlier than d. A range of the form d< or >d selects
52 all revisions dated later than d. If < or > is followed by = then
53 the ranges are inclusive, not exclusive. A range of the form d
54 selects the single, latest revision dated d or earlier. The
55 date/time strings d, d1, and d2 are in the free format explained in
56 co(1). Quoting is normally necessary, especially for < and >.
57 Note that the separator is a semicolon.
58 -l[lockers]
60 Print information about locked revisions only. In addition, if the
61 comma-separated list lockers of login names is given, ignore all
62 locks other than those held by the lockers. For example,
63 rlog -L -R -lwft RCS/* prints the name of RCS files locked by the
64 user wft.
65 -r[revisions]
67 prints information about revisions given in the comma-separated
68 list revisions of revisions and ranges. A range rev1:rev2 means
69 revisions rev1 to rev2 on the same branch, :rev means revisions
70 from the beginning of the branch up to and including rev, and rev:
71 means revisions starting with rev to the end of the branch contain‐
72 ing rev. An argument that is a branch means all revisions on that
73 branch. A range of branches means all revisions on the branches in
74 that range. A branch followed by a . means the latest revision in
75 that branch. A bare -r with no revisions means the latest revision
76 on the default branch, normally the trunk.
77 -sstates
79 prints information about revisions whose state attributes match one
80 of the states given in the comma-separated list states.
81 -w[logins]
83 prints information about revisions checked in by users with login
84 names appearing in the comma-separated list logins. If logins is
85 omitted, the user's login is assumed.
86 -T This option has no effect; it is present for compatibility with
88 other RCS commands.
89 -V Print RCS's version number.
91 -Vn Emulate RCS version n when generating logs. See co(1) for more.
93 -xsuffixes
95 Use suffixes to characterize RCS files. See ci(1) for details.
96 rlog prints the intersection of the revisions selected with the options
98 -d, -l, -s, and -w, intersected with the union of the revisions
99 selected by -b and -r.
100 -zzone specifies the date output format, and specifies the default time
102 zone for date in the -ddates option. The zone should be empty,
103 a numeric UTC offset, or the special string LT for local time.
104 The default is an empty zone, which uses the traditional RCS
105 format of UTC without any time zone indication and with slashes
106 separating the parts of the date; otherwise, times are output in
107 ISO 8601 format with time zone indication. For example, if
108 local time is January 11, 1990, 8pm Pacific Standard Time, eight
109 hours west of UTC, then the time is output as follows:
110 option time output
112 -z 1990/01/12 04:00:00 (default)
113 -zLT 1990-01-11 20:00:00-08
114 -z+05:30 1990-01-12 09:30:00+05:30
115
117 rlog -L -R RCS/*
118 rlog -L -h RCS/*
119 rlog -L -l RCS/*
120 rlog RCS/*
121 The first command prints the names of all RCS files in the subdirectory
123 RCS that have locks. The second command prints the headers of those
124 files, and the third prints the headers plus the log messages of the
125 locked revisions. The last command prints complete information.
126
128 RCSINIT
129 options prepended to the argument list, separated by spaces.
130 See ci(1) for details.
131
133 The exit status is zero if and only if all operations were successful.
134
136 Author: Walter F. Tichy.
137 Manual Page Revision: 5.9; Release Date: 1995/06/16.
138 Copyright © 1982, 1988, 1989 Walter F. Tichy.
139 Copyright © 1990, 1991, 1992, 1993, 1994, 1995 Paul Eggert.
140
142 ci(1), co(1), ident(1), rcs(1), rcsdiff(1), rcsintro(1), rcsmerge(1),
143 rcsfile(5)
144 Walter F. Tichy, RCS--A System for Version Control, Software--Practice
145 & Experience 15, 7 (July 1985), 637-654.
146
148 The separator for revision ranges in the -r option used to be - instead
149 of :, but this leads to confusion when symbolic names contain -. For
150 backwards compatibility rlog -r still supports the old - separator, but
151 it warns about this obsolete use.
152GNU 1995/06/16 RLOG(1)