Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On Fri, 6 Aug 2004 17:28:30 +0100, "Peter Crowther" <Peter.Crowther at melandra.com> wrote: >> From: Tony Hoyle [mailto:tmh at nodomain.org] >> It's actually possible to do something with CVSNT but it's not been >> implemented yet (time pressure plus distributed repositories don't >> seem to be that popular). It's not realtime synchronisation though as >> that would require super-smart software to handle the conflicts (which >> I doubt is possible with any SCM) > >Well, it *should* presumably be possible to use a (single or >distributed) lock service - probably a single service to start with. >That could be used as a low-bandwidth way of finding conflicts. Can't >say I'd fancy writing it though! > > - Peter That wouldn't solve it... User A in india modifies fileA and fileB, then commits to the india server User B in the US modifies file A and fileC then commits to the US server fileA now has a conflict. The servers can't be synced automatically because you can't solve it automatically. Manually it would just be User C (in charge of synchronisation) in the US does (suggested syntax...) cvs update -j :sspi:india:/cvs^HEAD Then fixes the conflict in fileA, then commits. Someone in india does the the same, and they're back in sync. Tony