Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Brian Smith wrote: > Sure, that would work. However, I will just note that on Windows the > distributing a .REG file is almost as easy and might be better for > centrally-managed installations. Not really. I frequently have to go onto peoples machines who only have wincvs 1.2 on and do command line stuff. I run cvs.exe off a public network share in that case - installation would be a hassle. Also with a config file I can keep the format the same on the unix version which makes documentation a lot easier too. Personally I'd rather not have either and just have it automatically detect, but supporting multiple protocols on a single dll makes that difficult on the client side - the server loads every protocol up anyway so that'll work without any help. > Unfortunately, testing with the current CVS tree still requires me to > merge my changes with yours because you added the negotiation stuff. I > will try to do the merge and then I'll send you a patch and we can both > test it out. I just want to get the wire protocol right, the rest can wait. rc2 needs releasing soon as there are fixes (like the cvs passwd stuff) that are needed so people can use the program properly. I expect rc2 will probably just become the release version - it's pretty stable now. > By the way, when 1.11.1.3 is released, will you please create a branch > for maintanance (bug-fixing only) purposes? Generally I just do a couple of release bugfixes until everyone is happy, then start another development cycle. I could create a branch if there was a really good reason for it... I'd like to avoid releasing off two branches though. Tony _______________________________________________ Cvsnt mailing list Cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs