M, Thanks. That is what I am doing while asking the list. I have one programmer that used a windows product before coming here and the two remote programmers really never used one. They have used SVN before but I think our setup is what the problem may be. They are supposed to take another look at SVN and let me know what are the bottlenecks to introducing this as our system of choice.
John J. Boris, Sr. JEN-A-SyS Administrator Archdiocese of Philadelphia Fax: 215-587-3525 "Remember! That light at the end of the tunnel Just might be the headlight of an oncoming train!" >>> Meenoo Shivdasani <mee...@gmail.com> 5/6/2010 11:28 AM >>> > Anyway I will look at the other products as well as looking back at > SVN. John, There's a matrix of subversion clients at http://en.wikipedia.org/wiki/Comparison_of_Subversion_clients which lists OS, license, and network protocols for each client. Pretty much all of them (and the subversion command line client itself) support svn over ssh. I don't know how up to date it is, but might be worth taking a look at. It may be worth trying to identify which facets of subversion were problematic to your developers and/or asking them to explain exactly how they like to work with their code so that you can come up with a list of requirements to work from. HTH, M _______________________________________________ Discuss mailing list Discuss@lopsa.org http://lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
