Firsing svn:eol-style=native on files with "binary" mime types?

[Aleksey Nogin <al...@nogin.org>]

I have a number of files that should use native eols, but should not be 
merged by subversion. It turns out that if I _first_ mark these files 
with a "non-text" mime-type, then subversion refuses to accept 
eol-style=native on them, complaining:

svn: File 'foo' has binary mime type property

Even --force does not help convince subversion that I know what I am 
doing here. So far, the only way to get around it that I've found is to 
remove the svn:mime-type, add svn:eol-style, and then put svn:mime-type 
back in, which is quite annoying.

Is there a better way? Should this be considered a bug? Is there an 
issue filed on this? Thanks!

-- 
Aleksey Nogin

Home Page: http://nogin.org/
E-Mail: nogin@cs.caltech.edu (office), aleksey@nogin.org (personal)
Office: Moore 04, tel: (626) 395-2200

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org