1RCSCLEAN(1) General Commands Manual RCSCLEAN(1)
2
6 rcsclean - clean up working files
7
9 rcsclean [options] [ file ... ]
10
12 rcsclean removes files that are not being worked on. rcsclean -u also
13 unlocks and removes files that are being worked on but have not
14 changed.
15 For each file given, rcsclean compares the working file and a revision
17 in the corresponding RCS file. If it finds a difference, it does noth‐
18 ing. Otherwise, it first unlocks the revision if the -u option is
19 given, and then removes the working file unless the working file is
20 writable and the revision is locked. It logs its actions by outputting
21 the corresponding rcs -u and rm -f commands on the standard output.
22 Files are paired as explained in ci(1). If no file is given, all work‐
24 ing files in the current directory are cleaned. Filenames matching an
25 RCS suffix denote RCS files; all others denote working files.
26 The number of the revision to which the working file is compared may be
28 attached to any of the options -n, -q, -r, or -u. If no revision num‐
29 ber is specified, then if the -u option is given and the caller has one
30 revision locked, rcsclean uses that revision; otherwise rcsclean uses
31 the latest revision on the default branch, normally the root.
32 rcsclean is useful for clean targets in makefiles. See also rcsd‐
34 iff(1), which prints out the differences, and ci(1), which normally
35 reverts to the previous revision if a file was not changed.
36
38 -ksubst
39 Use subst style keyword substitution when retrieving the revi‐
40 sion for comparison. See co(1) for details.
41 -n[rev]
43 Do not actually remove any files or unlock any revisions. Using
44 this option will tell you what rcsclean would do without actu‐
45 ally doing it.
46 -q[rev]
48 Do not log the actions taken on standard output.
49 -r[rev]
51 This option has no effect other than specifying the revision for
52 comparison.
53 -T Preserve the modification time on the RCS file even if the RCS
55 file changes because a lock is removed. This option can sup‐
56 press extensive recompilation caused by a make(1) dependency of
57 some other copy of the working file on the RCS file. Use this
58 option with care; it can suppress recompilation even when it is
59 needed, i.e. when the lock removal would mean a change to key‐
60 word strings in the other working file.
61 -u[rev]
63 Unlock the revision if it is locked and no difference is found.
64 -V Print RCS's version number.
66 -Vn Emulate RCS version n. See co(1) for details.
68 -xsuffixes
70 Use suffixes to characterize RCS files. See ci(1) for details.
71 -zzone Use zone as the time zone for keyword substitution; see co(1)
73 for details.
74
76 rcsclean *.c *.h
77 removes all working files ending in .c or .h that were not changed
79 since their checkout.
80 rcsclean
82 removes all working files in the current directory that were not
84 changed since their checkout.
85
87 rcsclean accesses files much as ci(1) does.
88
90 RCSINIT
91 Options prepended to the argument list, separated by spaces. A
92 backslash escapes spaces within an option. The RCSINIT options
93 are prepended to the argument lists of most RCS commands. Use‐
94 ful RCSINIT options include -q, -V, -x, and -z.
95 RCS_MEM_LIMIT
97 Normally, for speed, commands either memory map or copy into
98 memory the RCS file if its size is less than the memory-limit,
99 currently defaulting to ``unlimited''. Otherwise (or if the
100 initially-tried speedy ways fail), the commands fall back to
101 using standard i/o routines. You can adjust the memory limit by
102 setting RCS_MEM_LIMIT to a numeric value lim (measured in kilo‐
103 bytes). An empty value is silently ignored. As a side effect,
104 specifying RCS_MEM_LIMIT inhibits fall-back to slower routines.
105 TMPDIR Name of the temporary directory. If not set, the environment
107 variables TMP and TEMP are inspected instead and the first value
108 found is taken; if none of them are set, a host-dependent
109 default is used, typically /tmp.
110
112 The exit status is zero if and only if all operations were successful.
113 Missing working files and RCS files are silently ignored.
114
116 Author: Walter F. Tichy.
117 Manual Page Revision: 5.9.4; Release Date: 2018-07-15.
118 Copyright © 2010-2015 Thien-Thi Nguyen.
119 Copyright © 1990, 1991, 1992, 1993 Paul Eggert.
120 Copyright © 1982, 1988, 1989 Walter F. Tichy.
121
123 ci(1), co(1), ident(1), rcs(1), rcsdiff(1), rcsmerge(1), rlog(1), rcs‐
124 file(5).
125 Walter F. Tichy, RCS--A System for Version Control, Software--Practice
127 & Experience 15, 7 (July 1985), 637-654.
128 The full documentation for RCS is maintained as a Texinfo manual. If
130 the info(1) and RCS programs are properly installed at your site, the
131 command
132 info rcs
134 should give you access to the complete manual. Additionally, the RCS
136 homepage:
137 http://www.gnu.org/software/rcs/
139 has news and links to the latest release, development site, etc.
141
143 At least one file must be given in older Unix versions that do not pro‐
144 vide the needed directory scanning operations.
145GNU RCS 5.9.4 2018-07-15 RCSCLEAN(1)