head	1.4;
access;
symbols
	recovery_branch:1.4.0.2
	recovery_base:1.4;
locks; strict;
comment	@# @;


1.4
date	96.09.23.16.28.47;	author hartmans;	state Exp;
branches;
next	1.3;

1.3
date	96.09.23.16.27.28;	author hartmans;	state Exp;
branches;
next	1.2;

1.2
date	96.09.07.21.11.27;	author hartmans;	state Exp;
branches;
next	1.1;

1.1
date	96.09.07.20.57.51;	author hartmans;	state Exp;
branches;
next	;


desc
@@


1.4
log
@Generate test log message
@
text
@# Three different line formats are valid:
#	key	-a    aliases...
#	key [options] directory
#	key [options] directory files...
#
# Where "options" are composed of:
#	-i prog		Run "prog" on "cvs commit" from top-level of module.
#	-o prog		Run "prog" on "cvs checkout" of module.
#	-e prog		Run "prog" on "cvs export" of module.
#	-t prog		Run "prog" on "cvs rtag" of module.
#	-u prog		Run "prog" on "cvs update" of module.
#	-d dir		Place module in directory "dir" instead of module name.
#	-l		Top-level directory only -- do not recurse.
#
# NOTE:  If you change any of the "Run" options above, you'll have to
# release and re-checkout any working directories of these modules.
#
# And "directory" is a path to a directory relative to $CVSROOT.
#
# The "-a" option specifies an alias.  An alias is interpreted as if
# everything on the right of the "-a" had been typed on the command line.
#
# You can encode a module within a module by using the special '&'
# character to interpose another module into the current module.  This
# can be useful for creating a module that consists of many directories
# spread out over the entire source repository.
src	src@


1.3
log
@Force commit to generate log message
for test of log.pl
@
text
@@


1.2
log
@modules
@
text
@@


1.1
log
@initial checkin of modules
@
text
@d27 1
@
