-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [EMAIL PROTECTED] wrote: > This is in an academic environment. I was already pushing the envelope > to use version control, since people had to learn something new. (How > sad.) > Often people just keep emailing each other with the new versions, or > set up a web page that you can download the files from...
On further reflection, I realized that this is probably the source of your problems. Most likely, when they email or download the files, the files contain the line-ending convention of the person who posted them, and the files are not corrected before the recipient tries checking them in. Encourage the other users (how many are there, by the way?) to use CVS for transferring files to each other. It has the double benefit of automatically converting the line endings, and keeping track of intermediate versions. Sooner or later, their current habits are going to bite them in other ways. > I hope that I can get the committers to convert the files to unix > format themselves (prior to a commit) in the near future. The > pre-commit script then will be slightly modified to only do the > checking and refuse the commit. Or, you could simply put the modified script in place right away, and when the users complain, tell them to run unix2dos on the file and then check it in. - -- Jim Hyslop Dreampossible: Better software. Simply. http://www.dreampossible.ca Consulting * Mentoring * Training in C/C++ * OOD * SW Development & Practices * Version Management -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFED1p8LdDyDwyJw+MRAroRAKDyg0I8ina3nXS0ZyFoObHkZ8Y/DACgvbi7 GVXzY4yLShjJ7AcLTFS1P9Q= =LaCR -----END PGP SIGNATURE----- _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
