At 16:07 +0000 1/16/02, Kenneth Loafman wrote: >Rather than creating a new repository for code that's going to be >transferred, eventually, to a spin-off company, would it be easier to >create a module for them, then transfer the module, or should we create >a new repository.
Think of a repository as a modules + CVSROOT. The loginfo, commitinfo, etc. files in CVSROOT enforce certain policies for your development environment. If you want to use the same policies before transferring the code to the spin-off, then creating a new module is just fine. If you have to change the policies, then you should create a new repository. When you transfer the code module, remember to transfer any scripts from CVSROOT that are important to the code. If you think that there will be a lot of CVSROOT scripts to transfer, then it might be easier to create a separate repository from the start. Fred -- Fred Brehm, Sarnoff Corporation, [EMAIL PROTECTED] http://www.sarnoff.com/digital_video_informatics/vision_technology/index.asp _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
