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

Re: Recommended Subversion Repository Structure

From: Nico Kadel-Garcia <nkadel_at_comcast.net>
Date: 2006-03-25 18:31:06 CET

Steve Gardell wrote:
> Doesn't this just come down to the relationship between the projects?
> If one wants to have several projects that are in lock-step (maybe
> they are really more like "components" than projects) then the
> second makes the most sense. If one is layering things so that
> version N of projectA is supported by some set of versions of
> ProjectB, then the first makes the most sense.
>> -----Original Message-----
>> From: Jay Lessik [mailto:joemama77ca@yahoo.ca]
>> Sent: Friday, March 24, 2006 11:20 AM
>> To: users@subversion.tigris.org
>> Subject: Recommended Subversion Repository Structure
>> I'm new to subversion so forgive me if this question is newbie-ish...
>> I know that project repository structure has been discussed
>> on this list and I've read a lot of the posts, but I wasn't
>> able to find a clear answer to the question of which of the
>> following is better?
>> repository/
>> projectA/
>> trunk/
>> branches/
>> tags/
>> projectB/
>> trunk/
>> branches/
>> tags/

It's also useful if you are handling access to or responsibility for a
specific project. All have read-access, the tags have write access for only
a few people, and different projects have different usergroups.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Mar 25 18:31:46 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.