NameDateSize

..Today52

ChangeLogH A D28-Sep-200116.5 KiB

clmerge.inH A D28-Sep-20013.3 KiB

cln_hist.inH A D28-Sep-20011.9 KiB

commit_prep.inH A D28-Sep-20015.4 KiB

cvs2vendor.shH A D17-Mar-19974.4 KiB

cvs_acls.inH A D28-Sep-20015.1 KiB

cvscheck.manH A D17-Mar-19971.4 KiB

cvscheck.shH A D17-Mar-19972.2 KiB

cvshelp.manH A D17-Mar-199713.7 KiB

debug_check_log.shH A D28-Sep-20014.4 KiB

descend.manH A D17-Mar-19972.4 KiB

descend.shH A D17-Mar-19972.5 KiB

dirfns.sharH A D19-Dec-199511.1 KiB

intro.docH A D19-Dec-19953.9 KiB

log.inH A D28-Sep-20014.8 KiB

log_accum.inH A D28-Sep-200114.3 KiB

Makefile.amH A D30-Sep-20013.2 KiB

Makefile.inH A D30-Aug-201811.3 KiB

mfpipe.inH A D28-Sep-20011.8 KiB

rcs-to-cvs.shH A D17-Mar-19974.5 KiB

rcs2log.shH A D07-Aug-200117.3 KiB

rcs2sccs.shH A D17-Mar-19973.9 KiB

rcslock.inH A D28-Sep-20016.4 KiB

READMEH A D10-Jan-20194.7 KiB

sccs2rcs.inH A D28-Sep-20018.1 KiB

README

1This "contrib" directory is a place holder for code/scripts sent to me
2by contributors around the world.  This README file will be kept
3up-to-date from release to release.  BUT, we must point out that these
4contributions are really, REALLY UNSUPPORTED.  In fact, we probably
5don't even know what some of them really do.  We certainly do not
6guarantee to have tried them, or ported them to work with this CVS
7distribution.  If you have questions, your best bet is to contact the
8original author, but you should not necessarily expect a reply, since
9the author may not be available at the address given.
10
11USE AT YOUR OWN RISK -- and all that stuff.
12
13"Unsupported" also means that no one has volunteered to accept and check
14in changes to this directory.  So submissions for new scripts to add
15here are unlikely to be accepted.  Suggested changes to the existing
16scripts here conceivably might, but that isn't clear either, unless of
17course they come from the original author of the script.
18
19If you have some software that works with CVS that you wish to offer it
20is suggested that you make it available by FTP or HTTP and then announce
21it on the info-cvs mailing list.
22
23An attempt at a table of Contents for this directory:
24
25	README		This file.
26	log		A perl script suitable for including in your
27			$CVSROOT/CVSROOT/loginfo file for logging commit
28			changes.  Includes the RCS revision of the change
29			as part of the log.
30			Contributed by Kevin Samborn <samborn@sunrise.com>.
31	commit_prep	A perl script, to be combined with log_accum.pl, to
32	log_accum	provide for a way to combine the individual log
33			messages of a multi-directory "commit" into a
34			single log message, and mail the result somewhere.
35			Can also do other checks for $Id and that you are
36			committing the correct revision of the file.
37			Read the comments carefully.
38			Contributed by David Hampton <hampton@cisco.com>.
39	mfpipe		Another perl script for logging.  Allows you to
40			pipe the log message to a file and/or send mail
41			to some alias.
42			Contributed by John Clyne <clyne@niwot.scd.ucar.edu>.
43	rcs-to-cvs	Script to import sources that may have been under
44			RCS control already.
45			Contributed by Per Cederqvist <ceder@lysator.liu.se>.
46	cvscheck	Identifies files added, changed, or removed in a
47	cvscheck.man	checked out CVS tree; also notices unknown files.
48			Contributed by Lowell Skoog <fluke!lowell@uunet.uu.net>
49	cvshelp.man	An introductory manual page written by Lowell Skoog
50			<fluke!lowell@uunet.uu.net>.  It is most likely
51			out-of-date relative to CVS 1.3, but still may be
52			useful.
53	dirfns		A shar file which contains some code that might
54			help your system support opendir/readdir/closedir,
55			if it does not already.
56			Copied from the C-News distribution.
57	rcslock		A perl script that can be added to your commitinfo
58			file that tries to determine if your RCS file is
59			currently locked by someone else, as might be the
60			case for a binary file.
61			Contributed by John Rouillard <rouilj@cs.umb.edu>.
62	cvs_acls	A perl script that implements Access Control Lists
63			by using the "commitinfo" hook provided with the
64			"cvs commit" command.
65			Contributed by David G. Grubbs <dgg@ksr.com>.
66	descend		A shell script that can be used to recursively
67	descend.man	descend through a directory.  In CVS 1.2, this was
68			very useful, since many of the commands were not
69			recursive.  In CVS 1.3 (and later), however, most of
70			the commands are recursive.  However, this may still
71			come in handy.
72			Contributed by Lowell Skoog <fluke!lowell@uunet.uu.net>
73	cln_hist	A perl script to compress your
74			$CVSROOT/CVSROOT/history file, as it can grow quite
75			large after extended use.
76			Contributed by David G. Grubbs <dgg@ksr.com>
77	sccs2rcs	A C-shell script that can convert (some) SCCS files
78			into RCS files, retaining the info contained in the
79			SCCS file (like dates, author, and log message).
80			Contributed by Ken Cox <kenstir@viewlogic.com>.
81	intro.doc	A user's view of what you need to know to get
82			started with CVS.
83			Contributed by <Steven.Pemberton@cwi.nl>.
84	rcs2sccs	A shell script to convert simple RCS files into
85			SCCS files, originally gleaned off the network
86			somewhere (originally by "kenc") and modified by
87			Jerry Jelinek <jerry@rmtc.Central.Sun.COM> and
88			Brian Berliner <berliner@sun.com> to increase
89			robustness and add support for one-level of branches.
90	rcs2log		A shell script to create a ChangeLog-format file
91			given only a set of RCS files.
92			Contributed by Paul Eggert <eggert@twinsun.com>.
93 	clmerge		A perl script to handle merge conflicts in GNU
94			style ChangeLog files .
95			Contributed by Tom Tromey <tromey@busco.lanl.gov>.
96	cvs2vendor	A shell script to move changes from a repository
97			that was started without a vendor branch to one
98			that has a vendor branch.
99			Contributed by Greg A. Woods <woods@planix.com>
100