Late last week, I discovered the secret for doing remote work,
and merging the changes in.  What you do is first of all FREQ
GNUDIFF.ZIP and GNUPATCH.ZIP from 3:711/934.  The exes work 
under OS/2, I don't know about DOS.  What this gives you is two
commands:

1. diff.
2. patch.

Now let's say I put out MSGED/SQ 3.20, and two people send in
some changes to the same file.  If they use diff to send their
changes back, I can then use the patch command to merge in
their changes to the original.  Then once I know what their
changes are, I can merge them back into the development stream,
using cvs update.  I can do the same to the other person's
changes too.

It's well worth spending the effort to do some source code
control.  I just did my first "tag" a few minutes ago.  What I
did was tag all of PQWK245 with a tag "rel245" so that whenever
I want to find out what rel245 looked like, I can check it out.
Or alternatively, I can do a "cvs diff" to find out what has
changed between say rel245 and rel255, e.g.  It's all possible
with these tools.  

Don't wait any longer.  If you haven't FREQed these files, FREQ
them now.  If you only FREQ 5 files this year, you're not FREQing
enough.  Just do it - FREQ!  BFN.  Paul.
@EOT:

---