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 email@example.com.
Using the latest WinCVS (2.0.2-4 2005-11-11 -- is it really that old?) with the latest CVSNT (2.5.03.2382) on Windows XP 64-bit. It seems we had to upgrade to the newer CVSNT to get it to run on WinXP-64. CVS server is on a Linux machine and hasn't changed in quite a while. Our code is developed on Windows. Our main repository is a little odd, in that originally we uploaded files to the Linux machine via SSH/SCP and then checked them in.out of CVS on the Linux machine. As a result, when we now use WinCVS, we have to employ the "Use Unix LF" option to keep CVS from translating them the way it normally thinks it should because they were originally checked in untranslated. When we switched to the latest CVSNT, we started getting the error "cvs: Obsolete CVSUSEUNIXLF option used. Please update your client.". I understand this to mean that support for the CVSUSEUNIXLF option has been removed, but I can't find when or why this was done, or what we're supposed to be doing if we were employing that option. The CVSNT History link at the left side of the Wiki: http://www.cvsnt.org/wiki/ points to a page that isn't available anymore. I tried searching this mailing list, but could only do it manually, and didn't locate any discussion of the issue. Anyone have any advice? Feel free to cc me directly when you reply, as I get this list in digest form which might limit turnaround time in the discussion. -- Chris 'Xenon' Hanson | Xenon @ 3D Nature | http://www.3DNature.com/ "I set the wheels in motion, turn up all the machines, activate the programs, and run behind the scenes. I set the clouds in motion, turn up light and sound, activate the window, and watch the world go 'round." -Prime Mover, Rush.