[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: Blair Zajac <blair_at_orcaware.com>
Date: Mon, 08 Jun 2009 14:06:07 -0700

Nathan Nobbe wrote:
> On Mon, Jun 8, 2009 at 9:24 AM, Les Mikesell <lesmikesell_at_gmail.com
> <mailto:lesmikesell_at_gmail.com>> wrote:
> Marko Käning wrote:
> what are your users running as an operating system? in this
> situation, it
> sounds like a true dcvs would excel. and actually, if your
> users arent on
> windows, id wholeheartedly recommend git-svn.
> I'd also recommend to go for a real distributed VCS!
> I just learnt on SVK's (another DVCS) mailing list that git is
> actually even under windows now easy to use with msysGit
> (http://code.google.com/p/msysgit/)!
> Perhaps mercurial (www.selenic.com/mercurial
> <http://www.selenic.com/mercurial>) might be another alternative
> for you!
> Distributed VCS's can let you avoid network issues by working in
> isolation, but if your real goal is to allow a number of distributed
> team members to take advantage of each others updates as they are
> made you are going to have to deal with the network transfers anyway
> - and depending on the nature of the project you may really want a
> central authoritative repository.
> yes, you will eventually have to go over the network, but even then
> another advantage of dvcs is the inherent ability to compress data. im
> not sure if this affects the amount of data sent over the wire on sync
> operations, but it wouldnt surprise me if it did.

Subversion sends compressed data over the wire in both directions. There's no
advantage here for either system.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-08 23:08:48 CEST

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