On Feb 3, 2012, at 11:23, Johan Holmberg wrote: > But even if I don't understand exactly why I had these problems, they are > solved now (as I wrote in the previous mail).
The Subversion client is responsible for normalizing keywords and eol styles before sending the changes to the repository to be committed. If you used a broken Subversion client (such as git-svn), unnormalized content could have been written to the repository. To avoid this, you could write a pre-commit hook to prevent unnormalized content. Hopefully a future version of the Subversion server will do this for you, but at present, it does not. http://subversion.tigris.org/issues/show_bug.cgi?id=4065
