On May 17, 2009, at 06:14, Alexey Ivanov wrote:
>> To further clarify this moment, the svn:mime-type must be text/
>> for svn:eol-style to affect anything.
>> Look for the "Warning" block.
In my experience, Subversion will not let you set svn:eol-style if
the file is considered binary (by virtue of its svn:mime-type). Example:
$ svn propset svn:eol-style native foo.png
svn: File 'foo.png' has binary mime type property
> I think, that this could be some of my cases. Since I've trouble to
> attach mime-types-file in the Subversion config,
> mime types for files, with which I've worked, could be arbitrary or
> not set at all.
The mime types won't be arbitrary unless you've set them that way.
When you add a file, Subversion sets the file's mime type to whatever
your auto-props say to set it to. If you haven't defined auto-props
for this type of file, then Subversion sets the mime type to
application/octet-stream if it believes it to be a binary file,
otherwise it leaves the mime type blank and treats it as a text file.
If you somehow managed to set svn:eol-style on a binary file (perhaps
by loading a dumpfile, or by using the language bindings), I think
Subversion would happily convert the line endings of the file and
thus corrupt it. So you definitely should not attempt to set svn:eol-
style on a binary file.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-17 17:01:45 CEST