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

["Aaron D. Turner" <aturner@pobox.com>]

-----BEGIN PGP SIGNED MESSAGE-----



On Thu, 25 Mar 1999, Daniel E. Markle wrote:

> 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.  ;)

It's two problems:

1) I have to run two commands to get the file on the server.  That's one
too many.

2) Having so many rev numbers makes it virtually impossible to find the
rev you want.


I understand all the problems of "work arounds" but developing this way is
painful.  I need a middle ground.  What would make me happy is:

1)  Fix the script that moves files from CVS to the /home/http/...  so we
only need to run one command.

2)  Learn a way to overwrite a rev.  Ie, commit a file(s) without
incrementing the rev number.

I understand I wouldn't be able to go "back" to an overwritten rev, but
that's the idea.  

Later...


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNvr/RzM3jpXy1kJtAQFx+gP9EdNqqbIJKc/sf239EHB23am8Mr7QN6Zc
b78tMzbLvXmSPABvdnqzwkfW8pZOnV4PXiebxtYN79lZQVID47tlgnq2ArGD7KGs
Cr00TslRCv19sM1gmcJHVLg8PBb/Wow2lUlYN4Skgwz8yqF8wT2rG0Z7JYO6E0CT
TFaf6ZwZhQc=
=NM5C
-----END PGP SIGNATURE-----