SVN is an old source control system that depends on a centralized repository, while the distributed source control systems don't need it. SVN also has the disadvantage that it poluates every directory with a .svn directory, while the modern distributed source control systems like GIT or Mercurial create just a single .git or .hg under the main directory, and in that directory it keeps the entire repository. When using such a source control system, the programmer can update the repository even while he is offline, and after a time when he goes online again, he can update other repositories from other servers. The advantage of these systems is that they are also faster even when working with very big repositories. Octavian ----- Original Message ----- From: "Scott Granados" <scott@granados-llc.net> To: "Blind sysadmins list" <blind-sysadmins@lists.hodgsonfamily.org> Sent: Saturday, May 21, 2011 12:03 AM Subject: Re: [Blind-sysadmins] Distributed Version Control System
I would have pointed you at Subversion. What didn't it do that you wanted?
On May 20, 2011, at 1:51 PM, David Mehler wrote:
Hello, I'm looking for a version control system for a few up and coming personal projects, one already underway one to begin. Over the years I've tried tackling both cvs and svn as version control systems with no success. I'm therefor looking in to a distributed version control system I do plan to have other developers assisting or taking a machine away from my network and not allowing internet access to a server, so I'll need to go distributed. Things I need:
Good Windows and Linux support I'm going to either be working in both environments or have developers who will. For the windows I'd prefer a gui app that integrates in to windows explorer.
File and Directory renaming support I've read so much today my head is swimming but if I rename a file or a directory I want the version control system to track that. I know some do, some don't.
Central server A network or internet accessible server that developers can pull a copy of the current files, go offline and work distributed, and then come back online and commit changes.
Branching and merging Not sure about this one, but I've read that cvs and svn in particular make branching (cvs) and merging (svn) I hope I don't have those backwards difficult.
I've looked at:
1. Git 2. Mercurial 3. Monotone
I started out with many more, but those seem to be the ones that will best work. I was wondering after all that if anyone has any opinions pro conn on these three distributed version control systems? Or, others I might have missed that might work as well. I am preferential to open source.
Thanks a lot. Dave.
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins