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

RE: How can a project be divided up between two repositories?

From: Jeremy Mordkoff <jlm_at_ZeeVee.Com>
Date: Thu, 15 Oct 2009 12:42:54 -0400

> -----Original Message-----
> From: Tom Lenz [mailto:astonishenator_at_gmail.com]
> Sent: Thursday, October 15, 2009 3:44 AM
> Suppose I have two sets of files that I want under version control,
> A and Site B, containing files as follows:
> Site A:
> File_a
> File_b
> File_c
> File_d
> Site B:
> File_e
> File_b
> File_c
> File_d
> I want to find a way to specify:
> If a change is made to File_a, it applies only to Site A. Call this
Group 1.
> If a change is made to File_e, it applies only to Site B. Call this
> Group 2.
> If a change is made to File_b, File_c or File_d, the change gets
> to both Site A and Site B. Call this Group 3.
> The files have to be in a certain location relative to a directory
> structure. For example, File_a and File_e must be in the same
> Also, in some cases, File_a and File_e have the same name.
> From time to time it may turn out that I want to move a particular
> from Group 3 to Group 1 or Group 2.
> The way we're doing it now is that Site A is in one repository and
> B is in another repository, which works and is sort of simple, but it
> has a big disadvantage in that if files in Group 3 get changed, they
> must be manually copied to from one site to another. This is a little
> worse in our case because in reality there are more than two sites
> involved.

Have you considered using one repository and using the
--depth/--set-depth options to control which files are visible in work
spaces for each group of users?



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-15 18:43:46 CEST

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