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

Re: One data set - two repositories?

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Wed, 29 Oct 2014 17:54:37 -0500

On Wed, Oct 29, 2014 at 5:33 PM, Andreas Stieger <andreas.stieger_at_gmx.de> wrote:
> Hello,
> On 29/10/14 21:07, cl_at_qgenuity.com wrote:
>> I'm looking for a way to use Subversion to store data from a single data
>> set across two repositories. More specifically, I want to have one
>> repository which contains all of the data and a second that contains only
>> specific directories.
>> When I am at home, I will sync to the "complete" repository and when I am
>> traveling, I will sync to the "partial" repository.
>> How do I set this up so that the two repositories play nicely with each
>> other?
> svn being a centralized system, the disconnected two-way element of your
> scenario is not part of its design. The keywords below will help you
> work around:
> a) svnsync, (one way) which has provisions for partial syncs
> b) same, but switching the direction as required
> c) two repositories with remote merging
> d) two repositories with vendor branches

Or, if you are only concerned with committing/updating certain
subdirectories in a working copy when traveling, you don't need
different repositories for that. Just do what you need.
You could even make different 'top level' projects that that pull in
the directories you want via svn external properties. Updating from
the top level would update the whole tree of external references, but
you'd have to commit changes to them separately.

   Les Mikesell
Received on 2014-10-29 23:55:03 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.