Just curious, did you choose to set svn:eol-style to LF because the server where they're hosted requires that style? I usually store my text files using svn:eol-style=native, which has the nice effect of substituting newlines with the EOL style native to the system that performs the checkout. (i.e. - checking out on Linux results in Linux newlines, Windows for Windows, etc.) I believe the translation is handled by the SVN server, and the text is stored using whatever line ending style is convenient for the server.
HTH, - Quinn On Mar 23, 2009, at 10:26 AM, [email protected] wrote:
That did it. I had added an entry following a tip to have line feeds set to LF which also added the mime type application/x-httpd-php. Thanks. Thomas On Mar 23, 5:49 pm, Quinn Taylor <[email protected]> wrote:Since this occurs when adding new files, it seems that Subversion is assigning a binary MIME types behind your back. :-) This means thata property of the type svn:mime-type is added as metadata to the file.In Versions, click on the file, view info (Cmd-I) or File > Show Inspector, then click on "Show Raw Properties" at the bottom. You can remove or change the MIME type here for each file. The longer-term fix is to make sure that the [auto-props] section in~/.subversion/config is not set to assign a binary type to .php files.It's probably best to use text/plain, although you could experiment with the non-standard PHP types listed here: http://en.wikipedia.org/wiki/Internet_media_type BTW, this SVN config file only changes settings on the client (and in this case, only for your user on the machine), not the server. Auto-props are a really cool feature of Subversion, but if set incorrectly,they can cause confusion such as this. - Quinn
smime.p7s
Description: S/MIME cryptographic signature
