Re: testing code inside CVS, but not increase rev #?

["Daniel E. Markle" <syntax@ashtech.net>]

On Mon, Mar 22, 1999 at 10:23:56AM -0800, Aaron D. Turner wrote:
> > > This generates new versions of files in CVS very quickly.  Ie, rev numbers

This is really nothing to worry about.  CVS isn't going to run out of numbers
in the real number system anytime soon.  ;)

> > > What's the best way to upload code to the server, without increasing the
> > > rev number.  I assume that I won't be able to "go back", but that's fine,

As this would destroy the integrity of the CVS system, it is not allowed.
Right now, though, all new revisions are 1.x, whenever we do a commit to
tst/production, we can reset things to 2.x to keep things clean if you like.

> scp files directly into the directories and delete them after I'm done

This is a Bad Idea(tm), there are many things that can get royally messed up
here:

1. As soon as someone commits to CVS, your changes are wiped out.
2. Unless you set the group to cvs and set g+w, you will cause all sorts of
permissions problems for anyone using the proper procedure.  And having a file
open here when someone does a commit would be a Bad Thing (tm).
3. Imagine the havoc if a couple of people started doing things this way...

-- 
-------------------
Daniel E. Markle
syntax@ashtech.net
-------------------