enforcing LF-normalization for svn:eol-style=native files (issue #4065)

Last week a colleague managed to commit a non-LF-normalized
svn:eol-style=native file in our repository again. As explained in
issue #4065 [1], this causes all kinds of problems.

I suspect there might be a bug in SVNKit, some edge-case where it
doesn't correctly translate the to-be-committed files to
LF-termination. But regardless, I'd like to protect my repository. I
don't fully control the clients that people use, and those clients can
always have bugs, ...

So ... how hard would it be to fix issue #4065, making the server
enforce the right eol-ness for correct operation? It's a genuine
question, I have no idea :-).

[1] http://subversion.tigris.org/issues/show_bug.cgi?id=4065 - server
should enforce LF normalization for svn:eol-style=native files

-- 
Johan