Never having had the misfortune to work with Windows, I don't know the mechanism for handling line-end differences on entry into a CVS repository on a unix box. I assume you have to handle this on your end, because I occasionally see files with CRLF out of CVS repositories. Is this the burden of your question 2?
To clean up your files, you might try some perl.
perl -pi.bak -e 'BEGIN{undef $/};s/\r*\r\n/\n/g' file...
should work from a unix command line. How you achieve this in Windows I don't know. Once it's working, you can just use `-pi' instead of `-pi.bak'. The 'i' works on files in-place; any trailing characters are appended to the file name to create a backup file. Handy for testing. Obviously, the line above gives me LF-only line endings.
Peter
Jeremias Maerki wrote:
Hi there Before I'm going to work on the multi-threading issues I wanted to clear up a few patch submissions. While applying them I ran across several files that had CRCRLF endings instead of CRLF when checked out using WinCVS on a Windows box. I think I have successfully corrected those I ran into. Does anyone have a good idea how to... 1. identify files not having correct linevindingstlithoutckaving de opendeach an>every file? 2. enforce correct line endings?
-- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ "Lord, to whom shall we go?" --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
