On Feb 8, 2005, at 4:03 PM, kfogel@collab.net wrote:
> Ben Collins-Sussman <sussman@collab.net> writes:
>> If you set 'svn:eol-style = native' on a file (which you're probably
>> doing with auto-props), and then try to commit the file, svn will barf
>> if it discovers inconsistent line endings.
>>
>> Why? Because if it converted the line endings to all LF or all CRLF,
>> the conversion would be lossy. There's no way to get the original
>> file back. Subversion refuses to lose data. Therefore, it barfs and
>> demands that you fix the inconsistent line endings yourself.
>>
>> Be thankful that it's doing this, not angry.
>
> I think his objection is that it gets 20 minutes into the import, then
> dies on one file, and after you fix that file, maybe it will go 40
> minutes, then die on another file, and so on.
>
> It would be more user-friendly to report *all* the problem files after
> a single run. This might be complex to implement, but it's certainly
> possible, and I wouldn't be averse to an enhancement issue being filed
> about it. What do you think?
>
I'm not sure I understand the proposal. One runs 'svn import', and
then 20 minutes in, you see a message like
svn: file X has inconsistent newlines
svn: this commit will fail, but continuing to search for other such
files...
?
Perhaps a better solution is a tool to go into contrib/ which will scan
a directory for files with this problem. It can be used as a
"pre-flight" check before large imports.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 9 00:24:12 2005