The most complex source control system, and the fastest is GIT. Unfortunately, if you need to use the source control under both Linux and Windows, GIT is not so great because it doesn't work as well under Windows as under Linux because of the incompatibilities between the Windows command prompt and some of the parameters used by GIT. So the recommended distributed source control system for those who need to use it under both Linux and Windows is Mercurial. Mercurial is also pretty fast, although not as fast as GIT, and it is also not as complex as GIT, but this is not always a disadvantage, because actually it can be easier to use and it does everything most users need. Mercurial can be used as a centralized repository on a server. I access it on the server using SSH but if I remember well there is a web interface also. Just as for SVN there is TortoiseSVN, for GIT and Mercurial there is this graphical interface, however, I remember that I tried it for GIT but it was not accessible because it uses a graphical interface which is not accessible for JAWS. I don't remember if for Mercurial there is an accessible version, but it is possible to be just like for GIT. But who knows, maybe there is an accessible interface just like for SVN... Anyway, it is easier to use the command line interface for Mercurial, because Mercurial is easier to use than SVN... for example it doesn't track the directories at all, but only the file content, so you can create any directory anywhere and they will be tracked by Mercurial automaticly if they are under the directory that contains the .hg directory. The merges are also easy to do with Mercurial and also other operations. Octavian ----- Original Message ----- From: "David Mehler" To: "blind-sysadmins" Sent: Friday, May 20, 2011 11:51 PM Subject: [Blind-sysadmins] Distributed Version Control System

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