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

Re: trunk/branches/tags and projects w/components

From: Russ <rsivak_at_istandfor.com>
Date: 2006-10-11 01:48:05 CEST

As mentioned, its really what suits you, but you should think about branching.... Do you want to have one branch in which you will change code for multiple projects (are the projects related?). If so, then you probably want a too level tags, branches and trunk. Otherwise you should set up a too level folder for each project, and then have trunk, tags and branches under each of the projects. This way you are not forced to checkout the whole project tree and switches and merges will be faster.

Sent wirelessly via BlackBerry from T-Mobile.

-----Original Message-----
From: Greg Thomas <thomasgd@omc.bt.co.uk>
Date: Tue, 10 Oct 2006 17:32:27
To:"Walden H. Leverich" <WaldenL@techsoftinc.com>
Subject: Re: trunk/branches/tags and projects w/components

On Tue, 10 Oct 2006 12:22:08 -0400, "Walden H. Leverich"
<WaldenL@techsoftinc.com> wrote:

>In one case the trunk, branches and tags directories would be at the top
>level, and all "sub-projects" would be w/in the top level trunk. In the
>other case the different sub-projects would be at the top level, and
>each would have a trunk, branches and tags directory.

The answer is really whatever suits you. In my case, I have the
trunk/branch/tag under each project directory so I can easily control
access to each project.


This post represents the views of the author and does
not necessarily accurately represent the views of BT.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 11 02:01:09 2006

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.