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

Repository design for integrated projects

From: Björn Blissing <bjorn.blissing_at_vti.se>
Date: Fri, 14 Mar 2008 11:07:20 +0100

I am trying to set up a SVN repository for the projects we are working on. If we look at the projects at the directory level they are organised like this:

ProjectA
        SubfolderA
        SubfolderB
        SubfolderC
ProjectB
        SubfolderE
        SubfolderF
        SubfolferG

My problem is that SubfolderA and SubfolderE should be exactly the same, ie. a subproject so if any user changes a file in Subfolder A these changes should appear in SubfolderE as well when the user commits his changes.

So the logical structure is more like
ProjectA
        ProjectC
        SubfolderB
        SubfolderC
ProjectB
        ProjectC
        SubfolderF
        SubfolderG

How should my SVN repository be organized to best suit this requirement? Of course each project (A, B and C) should be able to have its own branches.

/Bjorn

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-14 11:07:46 CET

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.