[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: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-11-07 19:11:10 CET

On Nov 7, 2005, at 18:20, Jesse Erlbaum wrote:

> 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.

See, and I learned version control on Subversion, and now that I'm
trying to participate in some open-source projects that use CVS, I'm
totally baffled by CVS's non-directory-ish treatment of braches and
tags. :-) Gonna have to find me a CVS book.

> 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.)

Well, you can forget about that, because Subversion doesn't work like
that. ;-)

If the five development efforts are distinct, then you'll want to be
able to branch and tag them separately, so your layout 1. above seems
best.

---------------------------------------------------------------------
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:13:38 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.