Re: CVS checkout, excluding some files??
Hi Is there anyway to checkout the repository such that I can exclude some files?These files are needed for an older release but in the current version they are not needed.I know we can make a branch, but is there any other method to exclude just some files from checkout?They are in different directories. It is theoretically possible to hack the modules file, but the modules file has no effect on doing an update, so sooner or later somebody's going to do a cvs update -d and get all those files back again. I was involved in a situation where we actually didn't want the majority of files in the source tree, and never did get a satisfactory solution to the problem (and was laid off before I had any real bright ideas). However, you say that the files are needed for an older release, but not in the current version. Why not just remove the files in the CVS meaning of the word? (Remove the files from the sandbox, do a cvs rm on them, and commit.) Assuming the earlier release is tagged, you'll get all the files when checking out the earlier release, and not when checking out the current files. -- Now building a CVS reference site at http://www.thornleyware.com [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS checkout, excluding some files??
mmala wrote: Hi Is there anyway to checkout the repository such that I can exclude some files?These files are needed for an older release but in the current version they are not needed.I know we can make a branch, but is there any other method to exclude just some files from checkout?They are in different directories. There isn't a way to control which files you get with a checkout w/o specifying each directory or file by hand. If you tagged the older release, you can just cvs rm the unneeded files. A checkout or update will do the right thing. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS checkout, excluding some files??
mmala wrote: Hi Is there anyway to checkout the repository such that I can exclude some files?These files are needed for an older release but in the current version they are not needed.I know we can make a branch, but is there any other method to exclude just some files from checkout?They are in different directories. Thanks, Jeeva Sarma If the tag for the older release (you did tag the release, didn't you?) is only on the files you need, cvs checkout -rreleasetag will only get those files (as they were at the time of the release). I have used this method to get sets of files from a general test script baseline, where I just need a subset of those files for a formal test, i.e. I only tag the ones I know will be used during the formal test, then do a cvs checkout -rformal_test_tagN module If you need the files as they currently are I suppose you could do some kind of find in the checked out directory and pipe that to a cvs update -A fnames, as someone earlier noted an update would probably get all the other files too. -- I'd crawl over an acre of 'Visual This++' and 'Integrated Development That' to get to gcc, Emacs, and gdb. Thank you. -- Vance Petree, Virginia Power ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS checkout, excluding some files??
Hi Is there anyway to checkout the repository such that I can exclude some files?These files are needed for an older release but in the current version they are not needed.I know we can make a branch, but is there any other method to exclude just some files from checkout?They are in different directories. Thanks, Jeeva Sarma __ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
