[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: Miha Vitorovic <mvitorovic_at_nil.si>
Date: 2005-11-08 08:41:13 CET

"David Demner - Subversion" <svn@demner.com> wrote on 07.11.2005 19:28:56:

> > -Jesse-
> >
> Hi Jesse,
> There is a third option, which is the one I chose when migrating from
> /project_repository/trunk
> The advantage is that it will look like you described your CVS layout to
> be - each 'module' becomes a repository with distinct versions, tags,
> 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.

Wrong. You can - or will be able to in 1.3, I am not sure - if you put all
your repositories in one directory (e.g. /repositories), and then use
Apache front-end, and SVNParentPath config option. Apache is then able
list all repositories.


  Miha Vitorovic
  Inženir v tehničnem področju
  Customer Support Engineer
   NIL Data Communications,  Tivolska cesta 48,  1000 Ljubljana,  Slovenia
   Phone +386 1 4746 500      Fax +386 1 4746 501     http://www.NIL.si
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 8 08:43:26 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.