> -----Original Message----- > From: Arthur Barrett [mailto:[email protected]] > Sent: Sunday, April 22, 2012 11:18 PM > To: Bulgrien, Kevin; giggzounet; [email protected] > Subject: RE: How to disable the cvs versioning for a specific > binary file inour program CVS repository > > Guillaume, > > What version of CVS are you using? Which version on the client, which > on the server? > > > > These archives can be quite big. I don't want that the CVS > > > make a version for each one (it takes too much place). But I want > > > that these test cases stay in the CVS repository and that they are > > > downloaded, if I do a checkout. Is that possible ? > > > > There is no way to use CVS to store a file without a > > revision. > > It depends on the version of CVS ;)
>From what has been posted on-list so many times, one might easily have thought you agreed that CVS did not do this: > -----Original Message----- <snip> > On Behalf Of Arthur Barrett > Sent: Sunday, February 19, 2012 9:59 PM <snip> > Note: if you are using CVS 2.x or CVSNT, then I recommend you contact > the vendor (March Hare Software) for support/training, CVSNT > is NoT CVS. ;-) > If you are using CVSNT (CVS 2.x) on linux, mac, solaris, hpux > or windows > then you just use the -1 keyword expansion option: > http://march-hare.com/library/cvsnt/Substitution-modes.html > > > If you then use something like `cvs admin -o 1.1 test_cases.tgz`, > > Beware of using 'cvs admin' arbitrarily, it's an 'admin' > option, and (in > my opinion) not designed for 'day to day' use. I.e.: before running > 'cvs admin' I always make sure I've got a backup of the repository. The original post did already make it quite clear this was dangerous, but then there is no particular harm in underscoring that fact. This message and/or attachments may include information subject to GD Corporate Policy 07-105 and is intended to be accessed only by authorized personnel of General Dynamics and approved service providers. Use, storage and transmission are governed by General Dynamics and its policies. Contractual restrictions apply to third parties. Recipients should refer to the policies or contract to determine proper handling. Unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender and destroy all copies of the original message.
