On Tue, Aug 26, 2008 at 10:53 AM, Roberto Mello <[EMAIL PROTECTED]> wrote: > You are describing the definition of a distributed revision control > system. SVN is not one of them, but there's a client (svk) that's add > distributed capabilities. I haven't used svk but such a fundamental > change to the design of the RCS seems like could only be added in a > hackish way, and partially.
SVK does lack part of the functionality of a full distributed rcs, but is sufficient for most users. It has the added benefit of compatibility with any existing SVN repo... As far as hackish: It doesn't seem hackish. It uses a mirror repo (depot) on the local machine, and does a great job of merging changes back and forth between that and the main SVN repo. It doesn't have the fine-grained control of other distributed solutions though as far as I can tell, there's no way to push or pull only portions of a branch when merging changes across branches or repos. It seems like this is halfway between. It's not as powerful as a full distributed revision control system, but it's cleaner and better suited to branching, multiple developers and complicated apps than SVN. Why not give it a shot? You can use it with existing SVN repos :) justin -- http://justinhileman.com _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
