testing code inside CVS, but not increase rev #?

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

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


Mostly directed at Daniel, but anyone feel free to chime in.

Q:  I tend to write in small sections, test, little more code, test, etc.
This generates new versions of files in CVS very quickly.  Ie, rev numbers
increase very quickly.  I'd rather just log new revisions when major
changes are completed or once per coding session.

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,
'cuz generally I'm just commenting out code I don't want anyways.


- -- 
Aaron Turner           | Either which way, one half dozen or another. 
aturner@pobox.com      | Check out the Red Hat Linux User's FAQ Online!
www.pobox.com/~aturner | http://www.pobox.com/~aturner/RedHat-FAQ/
All emails from this account are PGP signed.  Lack of a signature is "bad".
PGP Key fingerprint = FB E1 CE ED 57 E4 AB 80  59 6E 60 BF 45 1B 20 E8



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

iQCVAwUBNvLzJTM3jpXy1kJtAQE0AgQAvAw/ivbVXgyWvDnBuFoj8D2+WYGOK/AL
ZbxBDVGlwdei9JLsgYej4S5f1ACDa9tSG2uhUng0Funmiux7+DZhkrsHTyO6G8x6
SJc3wxAtW+/QF30x5FkdnFiXLCe0RWQTLwn2A24ZiRyufp0ZgxKOiBr0P3D8EFs5
Arh11xxt9vs=
=dZNK
-----END PGP SIGNATURE-----