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

Re: Howto handle remote repository creation in a Multi-Repository scenario

From: Arnauld Van Muysewinkel <arnauldvm_at_gmail.com>
Date: 2007-06-14 20:13:59 CEST

2007/6/14, Ryan Schmidt <subversion-2007b@ryandesign.com>:
> On Jun 14, 2007, at 08:29, schönfeld / in-medias-res.com wrote:
> > Andy Levy wrote:
> > Subversion talks about two variants of providing repositories. One per
> > project, or one for several projects. I would like to use the first
> > variant, but i anyway need a way to be flexible with this. What I am
> > asking for, is if there is a solution for my dillema, or not. I am not
> > asking for you to agree on how much significance i put into the
> > revision number.
> I was also going to suggest that you should reconsider using a single
> repository for everything. Not only would i solve the problem of
> remote repository creation, but it would enable you to share code
> between projects, should that need ever arise. If you have every
> project in its own repository, you won't be sharing code between them
> -- at least, not preserving history.



Note that there can be some inconvenient of putting all projects in
the same repository.
For example the revision graph function of TortoiseSVN gets slower and
slower when the repository becomes bigger.

Example: In my work place the admin took the decision to create one
repository by team, with all the projects of a team in the same repo.
With 1000+ revisions it took 3-4 minutes to get any revision graph.
Last week I migrated a big project of 6000+ revisions from CVS. Now we
have 7000+ revisions and the revision graph takes almost 15'. Not
quite usable.

Arnauld Van Muysewinkel
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 14 20:14:24 2007

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.