Adding files with Inconsistent EOL markers

When adding sources from large popular open source projects to my local repo,
(e.g. grundlett_at_spidey2:~/work/oasis/vendorsrc/knowledgetree$ svn add
3.5.2a-Release) I end up with errors that alert me that a file just added has
inconsistend end of line markers. This causes the side-effect that the
recursive add stops before completing. Would the 'quiet' option supress
these errors so that the recursive add completes through the project tree?

My workaround is to use status to find 'unknown' files and add them:
svn st ./3.5.2b-Release | egrep ^\\? | cut -d ' ' -f7 | xargs svn add

In a similar vein, would there be a good way to detect inconsistent EOL
markers prior to adding?

I have used dos2unix to correct the EOL markers in the files that triggered
the warning, but this change isn't noticed by "svn status" because the files
are binary equal. This means that I can't checkin the 'corrected' file. So
I'm afraid that for project sources that I want to export, I'll still get
mixed EOL

-- 
Gregory S. Rundlett
Manager, Technology Services
OASIS www.oasis-open.org
+1 (978) 667-5115 x 205
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org