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

Re: Repository structure advice

From: Blair Zajac <blair_at_orcaware.com>
Date: Thu, 14 Feb 2008 20:03:57 -0800

On Feb 14, 2008, at 6:52 PM, Chris Morris wrote:

> If this is a FAQ somewhere, please redirect me.
>
> Working at a shop with several products/codebases. Been running CVS
> for many of them, SourceSafe for the rest - and currently porting to
> SVN. Each codebase will need its own release branches (following the
> simple Prag Version Control release branch approach).
>
> Looking for any practical pros/cons of having one repository with
> all products/codebases in it -- or many repositories, one per
> product/codebase.

Use one repository and have your trunk/tags/branches under each
separate project. It's much easier to manage and if you ever want to
move projects around, you can do it without dumping and loading.

If you have different styles of data in one, say code, versus large
graphics in another, then you can split them up.

Regards,
Blair

-- 
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<blair_at_orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-15 05:04:26 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.