1.We are currently working on a large project now. As the project is currently under way, we are constantly making changes to the codes, with different people changing different part of the codes. In this situation, what is the best way to start implementing CVS? I was thinking of establishing a reference version, create a new module in CVS for this version, and have everybody checks out the version and start working from there. Is there a better way to do this?
2. As our project is very large, with millions of source files (literally), performing cvs release and checking out the whole project everytime are certainly not feasible. To overcome this, I was thinking of letting each programmer works on his/her own part of the code, so after the initial checking out of the whole project (as described in my first question), each programmer will only modify/commit his/her own codes. The drawback of this is of course nobody will have the complete newest version of the project. Is there a better way to do this? Thanks! _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
