On Wed, Oct 15, 2008 at 06:16, Andy Law <[EMAIL PROTECTED]> wrote: > Stefan Fritz-2 wrote: >> >>>>The main clincher is that we generally run all our sub-modules as > children >>>>of a parent super-module. That's only possible with the root approach. >> >> or you define trunk/tags/branches per module-group instead of per project >> as you would do for standalone projects ;-) > > If your projects genuinely are stand-alone projects then I would suggest > that you create separate repositories for each of them, although that may be > harder to do if you already have history within an existing repository. I > have not done so, but I imagine that it must be possible to clone a > repository and then remove extra stuff from each copy such that you reduce > to 1 project per repo?
You shouldn't create multiple repositories without *very* good reasons. Multiple repositories just means having to duplicate authentication, backup setup, etcetera. Moreover, any kind of copying between projects is much harder that way. If you are working on multiple projects you'll eventually run into refactoring cases where you want multiple projects to reuse some shared code. That's a no-brainer in one repository but all but impossible (i.e. without losing history) in multiple repositories. And what do you gain? There's little advantage to having a repository per project. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
