RCSCLEAN(1) RCSCLEAN(1)
NAME
rcsclean - clean up working files
SYNOPSIS
rcsclean [options] [ file(1,n) ... ]
DESCRIPTION
rcsclean removes files that are not being worked on. rcsclean -u also
unlocks and removes files that are being worked on but have not
changed.
For each file(1,n) given, rcsclean compares the working file(1,n) and a revision
in(1,8) the corresponding RCS file. If it finds a difference, it does noth-
ing. Otherwise, it first unlocks the revision if(3,n) the -u option is
given, and then removes the working file(1,n) unless the working file(1,n) is
writable and the revision is locked. It logs its actions by outputting
the corresponding rcs -u and rm -f commands on the standard output.
Files are paired as explained in(1,8) ci(1). If no file(1,n) is given, all work-
ing files in(1,8) the current directory are cleaned. Pathnames matching an
RCS suffix denote RCS files; all others denote working files.
The number of the revision to which the working file(1,n) is compared may be
attached to any of the options -n, -q, -r, or -u. If no revision num-
ber is specified, then if(3,n) the -u option is given and the caller has one
revision locked, rcsclean uses that revision; otherwise rcsclean uses
the latest revision on the default branch, normally the root.
rcsclean is useful for clean targets in(1,8) makefiles. See also rcsd-
iff(1), which prints out the differences, and ci(1), which normally
reverts to the previous revision if(3,n) a file(1,n) was not changed.
OPTIONS
-ksubst
Use subst style keyword substitution when retrieving the revi-
sion for comparison. See co(1) for details.
-n[rev]
Do not actually remove any files or unlock any revisions. Using
this option will tell you what rcsclean would do without actu-
ally doing it.
-q[rev]
Do not log the actions taken on standard output.
-r[rev]
This option has no effect other than specifying the revision for
comparison.
-T Preserve the modification time(1,2,n) on the RCS file(1,n) even if(3,n) the RCS
file(1,n) changes because a lock is removed. This option can sup-
press extensive recompilation caused by a make(1) dependency of
some other copy of the working file(1,n) on the RCS file. Use this
option with care; it can suppress recompilation even when it is
needed, i.e. when the lock removal would mean a change to key-
word strings in(1,8) the other working file.
-u[rev]
Unlock the revision if(3,n) it is locked and no difference is found.
-V Print RCS's version(1,3,5) number.
-Vn Emulate RCS version(1,3,5) n. See co(1) for details.
-xsuffixes
Use suffixes to characterize RCS files. See ci(1) for details.
-zzone Use zone as the time(1,2,n) zone for keyword substitution; see co(1)
for details.
EXAMPLES
rcsclean *.c *.h
removes all working files ending in(1,8) .c or .h that were not changed
since their checkout.
rcsclean
removes all working files in(1,8) the current directory that were not
changed since their checkout.
FILES
rcsclean accesses files much as ci(1) does.
ENVIRONMENT
RCSINIT
options prepended to the argument list, separated by spaces. A
backslash escapes spaces within an option. The RCSINIT options
are prepended to the argument lists of most RCS commands. Use-
ful RCSINIT options include -q, -V, -x, and -z.
DIAGNOSTICS
The exit(3,n,1 builtins) status is zero if(3,n) and only if(3,n) all operations were successful.
Missing working files and RCS files are silently ignored.
IDENTIFICATION
Author: Walter F. Tichy.
Manual Page Revision: 1.12; Release Date: 1993/11/03.
Copyright 1982, 1988, 1989 Walter F. Tichy.
Copyright 1990, 1991, 1992, 1993 Paul Eggert.
SEE ALSO
ci(1), co(1), ident(1), rcs(1), rcsdiff(1), rcsintro(1), rcsmerge(1),
rlog(1), rcsfile(5)
Walter F. Tichy, RCS--A System for Version Control, Software--Practice
& Experience 15, 7 (July 1985), 637-654.
BUGS
At least one file(1,n) must be given in(1,8) older Unix versions that do not pro-
vide the needed directory scanning operations.
GNU 1993/11/03 RCSCLEAN(1)