# PUTTING CODE INTO CVS at DO
#
#############
# 
# You have edited your code, and it compiles,
# builds, and tests fine with 

gmake all
gmake test

# Make sure CVS wasn't updated while you were
# working on your private version:

cvs -n update

# This does a test of your code against the archive.
# The differing files will be listed with a code letter:
#
# U means an update exists in CVS that you don't have
# M means your file is newer than CVS
# C means your file differs from CVS and both are new
# no listing means your files are the same.

# Ideally you see only "M" or nothing.  If you see "U" then

cvs update

# will actually copy the U files from CVS into your local
# area.  You should test build again.  Be careful with
# this command!  CVS is usually smart but can really 
# scramble code if it gets confused.  Make a copy of 
# the files that CVS will update.

############

# Edit the VERSION file so the new version is
# incremented by one.  Do 

cvs -n update

# and make sure VERSION appears as "M"


ctcommit

# This puts you into the "vi" editor by default.
# Put in the version number and a meaningful comment about
# you changes.

# If you have permission to write to the archive, you
# will see messages indicating success.