[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Multiple repositories per project

From: <blackhole_at_collab.net>
Date: Wed, 4 Feb 2009 01:14:37 -0800 (PST)

thanks for your helpful comments. here are some more details:

- this policy did certainly not arise from customer requirements. if there are internal requirements for this, then i am not aware of them (but most likely there a none).

- it's also not security related i think. all repositories of a project have the same permissions and are equally accessible by the project members (they are accessed through ssh+svn).

Reedick, Andrew wrote:
> It's also harder to checkout, export, or otherwise pull code from three
> different repositories. You have to have three workspaces instead of
> one. If you need to research a problem, you have three log histories to
> go through. With one repository, I can say "show me what's happened
> since day Foo" to see if Alice checked in the corrected documentation
> before or after the code drop. With three repositories, you have to
> integrate three timelines into one timeline.

thanks, these are the arguments i was looking for.

> As others have hinted, turn the question around. What is the benefit of
> having three repositories?

i tried that already, but got only obscure answers. so i figured i have to come up with arguments for *not* having multiple repositories in one project first.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-04 14:24:44 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.