|
Subversion considers its futureSubversion considers its futurePosted May 1, 2008 8:24 UTC (Thu) by boudewijn (subscriber, #14185)In reply to: Subversion considers its future by dbnichol Parent article: Subversion considers its future
I've just managed to convert my workplace from Team Coherence (an obscure, locking-not-merging, revision control system to subversion :-). It took me six months to convince my co-workers that it would be a good idea. Git, bzr or mercurial would have taken much longer, especially since I don't actually understand myself how the interaction between developers on a team working towards a common release really works. At least, not without someone blessed to produce the final source tree and thus having to go through all patches.
(Log in to post comments)
Subversion considers its future Posted May 1, 2008 9:30 UTC (Thu) by joib (guest, #8541) [Link] You just designate one repo as the canonical one, and tell everyone to push their changes there if they want their code to be part of the release. The canonical repo is thus the equivalent of THE repo in a centralized VCS like subversion.
|
Copyright © 2008, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds
Powered by Rackspace Managed Hosting.