Strategies for projects/branches layout

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-

--
 
Jesse Erlbaum
The Erlbaum Group
jesse@erlbaum.net
Phone: 212-684-6161
Fax: 212-684-6226
 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org