Re: Adding files with Inconsistent EOL markers

>>>>> "Greg" == Greg Rundlett <greg.rundlett_at_oasis-open.org> writes:

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

I don't think so. It sure would be nice to have a way to say "keep
going". Or better yet, a way to say "don't tell me, just fix it".

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

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

Search for files that contain both \r\n and [^\r]\n ?

 Greg> I have used dos2unix to correct the EOL markers in the files
 Greg> that triggered the warning, but this change isn't noticed by
 Greg> "svn status" because the files are binary equal.

That's strange. If dos2unix actually does something (there were dos
line-endings in the original file) then the files are NOT binary equal
and svn status should show that.

    paul

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-07 19:53:21 CEST