Seperate modules are better IMHO.
You can have modules included in eachother automagically, like:
cvsroot/lib
cvroot/project
You can set CVS to check out lib as if it was inside project.
This may help you : http://www.cvshome.org/docs/manual/cvs_18.html#SEC154
On Wed, May 16, 2001 at 12:09:50PM -0700, Harkins, Jim wrote:
> Assuming you're going to use CVS for several projects in your network, is it
> better to have 1 repository with multiple projects, or multiple repositories
> containing a single project? I don't mean project in the CVS sense, I mean
> it in the customer-signed-a-contract sense. Projects tend to overlap a bit.
> Most are based on a linux kernel, most have custom device drivers. They
> also differ in some significant ways. We have multiple Linux kernel
> version, different CPUs (StrongARM, SH4, Celeron, etc).
>
> jim
>
> _______________________________________________
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
