RCSFREEZE(1) UNIX Programmer's Manual RCSFREEZE(1)
rcsfreeze - freeze a configuration of sources checked in under RCS
rcsfreeze assigns a symbolic revision number to a set of RCS files that form a valid configuration. The idea is to run rcsfreeze each time a new version is checked in. A unique symbolic name (C_number, where number is increased each time rcsfreeze is run) is then assigned to the most recent revision of each RCS file of the main trunk. An optional name argument to rcsfreeze gives a symbolic name to the configuration. The unique identifier is still gen- erated and is listed in the log file but it will not appear as part of the symbolic revision name in the actual RCS files. A log message is requested from the user for future refer- ence. The shell script works only on all RCS files at one time. All changed files must be checked in already. Run rcsclean(1) first and see whether any sources remain in the current directory.
RCS/.rcsfreeze.ver version number RCS/.rcsfreeze.log log messages, most recent first
Stephan v. Bechtolsheim
co(1), rcs(1), rcsclean(1), rlog(1)
rcsfreeze does not check whether any sources are checked out and modified. Although both source file names and RCS file names are accepted, they are not paired as usual with RCS commands. Error checking is rudimentary. GNU 1990/11/13 1 RCSFREEZE(1) UNIX Programmer's Manual RCSFREEZE(1) rcsfreeze is just an optional example shell script, and should not be taken too seriously. See CVS for a more com- plete solution. GNU 1990/11/13 2
Generated on 2013-04-27 00:20:00 by $MirOS: src/scripts/roff2htm,v 1.77 2013/01/01 20:49:09 tg Exp $
These manual pages and other documentation are copyrighted by their respective writers;
their source is available at our CVSweb,
AnonCVS, and other mirrors. The rest is Copyright © 2002‒2013 The MirOS Project, Germany.
This product includes material provided by Thorsten Glaser.
This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report – diffs preferred.