Hi, I have some directories or files in production and development servers which are not under CVS control. Also there are some files which are there in production and not in development. Now I am planning to arrange or keep all these directories and files from production and development into one CVS repository which looks something like development and production environments inside CVS repository. There are only some files in some modules that gets changed, as this repository is not a project related. This repository is just for Tech & Ops to maintain its automated scripts, documents, configurations and software on a central server. Thanks for the responses which says go for branching. Branching looks like more cumbersome to me as the code or scripts will not change as frequently as it changes in developing a particular project.
Any other ways, advices on how to start with or how to go for branching limitedly so that it makes maintenance easy. Thanks, -Raghav _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
