2010/3/23, Daniel Stenberg wrote:

> A, B and C can sync up with the ME branch at any time and thus A B and C
> all get each other's changes once they've been deemed to go public.

I suppose that I was expecting to much. It seems that version control
systems are still in the dark-age relative to what database systems
have already achieved long time ago relative to things such as
'two-phase commit', 'multi-database transactions' , database
partitioning across systems and online and offline database
replication.

It seems that version control systems use the term 'distributed'
simply as a buzzword to indicate its capability to 'manually' get or
transmit changes from a 'same-kind' version control system. After all
someone has to push or pull.

Even CVS is distributed. You setup a CVS repo and commit all you want.
I can setup another CVS repo with all the contents of yours. I work on
mine all I want, and when the moment arrives to place my changes on
yours I can do it.

A poor man's replication system could equally be setup for CVS or git
using post commit hooks. But if a clash arises, which is more likely
on a very busy repos, manual aid is equally required.

Or does someone know of a VCS capable of doing multi-repo transactions
out there, commercial or not?

-- 
-=[Yang]=-
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html