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

Re: Path structure

From: Russ Brown <pickscrape_at_gmail.com>
Date: 2005-06-26 09:33:50 CEST

Adrian Hoe wrote:
> I have the same thought of Jon Cosby. Why do we need "trunk" and "branches"?
> Instead of
> project/
> calc/
> trunk/
> tags/
> branches/
> why not using this
> project/
> calc/
> Unless you have some slightly different set of specifications
> (requirements), otherwise, I don't see the necessity to use the former.
> I'm using the later and that's sufficient.
> But I don't see any problem using both.
> My 0.02. Cheers.

The directory structure is entirely up to you. However, if you are going
to want to create branches for your project, then you're going to need
somewhere to put them. Hence the 'branches' directory.

For example, where I work we currently don't bother with a tags
directory, because we don't need them, but we do have a releases
directory, which in our case is like a branch but serves a different

The Subversion Book shows that payout because it's flexible and provides
the features available in CVS.

You can choose your on path... ;-)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jun 26 09:35:52 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.