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

RE: .NET project source tree organization question

From: Gavin Lambert <gavinl_at_compacsort.com>
Date: 2006-09-15 03:37:17 CEST

Quoth Jiho Han <mailto:jhan@InfinityInfo.com>:
> It seems to me, more and more I think about it, it makes
> sense to branch at the solution level because a solution is
> the end product after all. If any of the projects are being
> reused elsewhere, then I could create another "solution" that
> contains trunk, branches, and tags. And perhaps use the
> Externals concept. I'm also beginning to wonder whether it's
> really necessary to have the trios. For example, perhaps
> trunk could be eliminated since the main folder will be the "trunk".

If you don't anticipate wanting to use branches and/or tags, then by all
means, don't create a trunk folder if you don't want one. You can
always add them in later on if you change your mind.

(The only real purpose for the 'trunk' folder is to separate the
contents from the 'branches'/'tags' folders. You definitely don't want
to have branches/tag folders within your "trunk" (whatever you call it)
-- otherwise you'll be forced to checkout every single branch/tag each
time, which is just a pain in the butt.)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 15 03:37:53 2006

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