I have recompiled CVS and made a couple of changes, and included
the following documentation.  The archive is available for FREQ
as CVSPE.ZIP from 3:711/934.  BFN.  Paul.


Date released: 1996-03-17

This archive was created by Paul Edwards, 3:711/934{at}fidonet.
It is a port of CVS13SRC.ZIP created by Lutz Grueneberg.  The
problems I had with CVS13SRC.ZIP was:

1. It didn't compile under EMX 0.9b properly.
2. It needed a lot of rubbish (shell, etc etc) in order to make it.
3. It used yacc which most people wouldn't have.
4. The date format it used was American.  I changed it to use the
   ISO date format YYYY-MM-DD.

I have called my archive CVSPE and include source and binary.  You
should obtain CVS13SRC.ZIP and the original CVS 1.3 distribution
if you want all the original source and documentation etc.  The
stuff in the DOC directory is all the licensing agreement etc.  All
the changes I have made, including this documentation, are public
domain.  The original archive is not public domain though.

To recompile this stuff, you need to go to the lib subdirectory
and type "nmake" or some other suitable make program, and then
go the src directory and do the same.  You will need to have
EMX 0.9b installed.

Basically you need to copy *.EXE into your path somewhere, and
then:

set LOGNAME=your_name
set EDITOR=e       (Or whatever your editor is)
set CVSROOT=e:\cvs    (Wherever you want to put your repository)


Then, say you are working on an application called "spread" for
"spreadsheet".  You would go to e:\cvs, mkdir spread, and then
go to some other location, such as e:\devel, and go:

cvs checkout spread
cd spread
create a file, fred.c
cvs commit fred.c
then make a change to fred.c
cvs diff fred.c will show you the changes
cvs commit fred.c to commit the changes
cvs log fred.c to see the descriptions you put in
cvs diff -r 1.1 -r 1.3 fred.c to find out what changes were made
  between revisions 1.1 and 1.3.
cvs diff -D 1996-03-13 -D 1996-03-16 fred.c to find out what
  changes were made between those two dates

Later on, you may find out about some brilliant things you can do
besides stock-standard controlling source code changes.  Don't read
the following until you have used CVS for a few months AND are
comfortable with it.

What you can do is tag a particular release, say you put out 
version 1.0 of your product, what you do is:

cvs tag release-1_00

Then a few months later

cvs tag release-2_00

Then 

cvs diff -r release-1_00 -r release-2_00 to find out the differences.

or 

cvs rdiff -r release-1_00 -r release-2_00 spread 

to create a patch file, which can allow you to just send the patch
file somewhere (presumably it is small), and the recipient can use
GNUPATCH to automatically update their own version of the file.

And then there's branching, where you can do:

cvs rtag release-1_00 spread
cvs tag -b -r john-1_00 spread
or better
 cvs rtag -r release-1_00 -b john-1_00 spread (use this!)
cvs tag -b -r bill-1_00 spread

When John sends in diffs...
cvs co -r john-1_00 spread (use this!)
cd spread
patch  * Origin: X (3:711/934.9)