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

Re: Strategies for projects/branches layout

From: David Demner - Subversion <svn_at_demner.com>
Date: 2005-11-07 19:28:56 CET

> Hi All --
> I'm moving from cvs to svn. In cvs I'm very accustomed to having one
> repository which holds multiple "modules" (to use cvs' parlance). Each
> module may then be tagged/branched as I see fit, after the fact.
> I'm thrown by svn's "directory-ish" treatment for branches and tags.
> Assume I have a repository which would house five related but distinct
> development efforts. It seems I have to choose from the start if I'm
> going to do:
> 1. .../repository/project/trunk/
> 2. .../repository/trunk/project/
> Suggestions? (At the moment I'm wishing that svn would treat branches
> and tags as additional dimensions, a la cvs.)
> Thanks,
> -Jesse-
Hi Jesse,

There is a third option, which is the one I chose when migrating from VSS:


The advantage is that it will look like you described your CVS layout to
be - each 'module' becomes a repository with distinct versions, tags, etc.
 The disadvantage is you can't enumerate all repositories on a server,
only directories within a repository. So that makes it a little more
awkward, but I think the benefits far outweigh.

Good luck,


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 7 19:33:29 2005

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.