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

Re: Distributed Subversion

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Mon, 08 Jun 2009 13:26:59 -0500

Nathan Nobbe wrote:
> Even with a distributed repository, sooner or later, you have to get
> the changes from the field back to the main repository, and if the
> network is slow, getting those changes back and forth will be slow.
> You could simply delay getting those changes from your remote
> locations, and only synchronize your repositories on a weekly basis,
> but then you run the risk of having merge problems.
> this is true, however, see above for the overall advantages of dvcs; esp
> in this case. offline working greatly increases performance (thats just
> one benefit).

Doesn't that sort-of assume that the people working offline aren't
wasting their time duplicating functionality that will have to be sorted
out when you get around to the merge? I'd expect performance to be best
for many projects when each programmer has fast access to the changes
others are making.

   Les Mikesell
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-08 20:28:50 CEST

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