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

Re: Two-Site Subversion Repository Setup Ideas

From: Andreas Krey <a.krey_at_gmx.de>
Date: Mon, 6 Jun 2011 13:07:19 +0200

On Sun, 05 Jun 2011 20:52:38 +0000, Nico Kadel-Garcia wrote:
> If they can't communicate electronically, you'll have to synchronize
> by physical media. Subversion is built on top of CVS paradighms, with
> a central repository. Parall, disconnected development *cannot work*
> with that model, not without someone manually resolving all the
> inevitable discrepancies and merge issues in parallel code lines.
> This is a case where you need to lay out what your limitations on
> connectivity really are: no connections? No patches transmitted? No
> auto-propagation? Nothing? Then they're two independent projects, with
> entire source trees.

That is not necessarily the case. I remember times when I just took the
tree of the customer, hacked at it in the company, and when I came back,
we took the original tree, the current customer tree and my modified
tree, and applied diff3 to it, getting all the necessary merges. (The
hard part is, of course, handling new and deleted files, but that wasn't
that much of an issue back then.)

Of course, I you do sync only once a week that precludes someone from
the other site agily adding some library feature to be used immediately.
Unless you get him physically to the other site, that is.


"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
Received on 2011-06-06 13:08:00 CEST

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.