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

Re: Cloning, branching, and cvs2svn

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2001-10-05 20:37:10 CEST

Steven Velez <svelez@alventive.com> writes:

> /core
> /branches
> Under branches we have several entries like
> /branches/v3.0.1
> /branches/v3.0.2
> .....
> Under core we have our "trunk" code stream which maps to our standard
> working space, but we have what we would consider several projects in this
> working space.
> Now I'm assuming we would end up creating the same structure in svn.
> However, I would like to know why one scheme is recommended over the other.

No hard-core reasons. I think that a majority of us simply think that
organizing by project, rather than branch, is just subjectively more

But this is a just a recommendation. You can organize a subversion
repository however you wish; your choice has no impact on subversion's
performance, only on how confused your users might be. Branches and
Tags are just ordinary directories, put wherever you want.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:44 2006

This is an archived mail posted to the Subversion Dev mailing list.