head	1.5;
access;
symbols;
locks; strict;
comment	@# @;


1.5
date	99.02.08.15.09.27;	author jsm;	state Exp;
branches;
next	1.4;

1.4
date	98.09.04.19.57.11;	author jsm;	state Exp;
branches;
next	1.3;

1.3
date	98.09.04.19.56.51;	author jsm;	state Exp;
branches;
next	1.2;

1.2
date	98.09.04.15.25.33;	author jsm;	state Exp;
branches;
next	1.1;

1.1
date	98.09.04.22.21.57;	author root;	state Exp;
branches;
next	;


desc
@@


1.5
log
@Standard sourceware CVS setup.
@
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.

CVSROOT CVSROOT
modules CVSROOT modules
webpages -a htdocs
@


1.4
log
@added the webpages entry back in.
@
text
@d28 2
a29 2
modules  -a CVSROOT/modules

@


1.3
log
@Me hacking--remove the webpages thing just to add it again in a second.
@
text
@d29 2
@


1.2
log
@Add standard modules (``modules'', ``webpages'').
@
text
@a27 3
CVSROOT CVSROOT

webpages -a htdocs
a28 1

@


1.1
log
@initial checkin
@
text
@d27 6
@

