[TYPO3-core] RFC #9474: Integrate OpenID authentication support to TYPO3

[Martin Kutschker]

Xavier Perseguers schrieb:
>>> enable-auto-props = yes
>>>
>>> and under [auto-props], list all file types you will be dealing with.
>>> You should have something like that
>>>
>>> [auto-props]
>>> *.css = svn:eol-style=native;svn:keywords=Date Author Revision Id
>>> *.gif = svn:mime-type=image/gif
>>> *.html = svn:eol-style=native;svn:keywords=Date Author Revision Id
>>> *.jpg = svn:mime-type=image/jpeg
>>> *.js = svn:eol-style=native;svn:keywords=Date Author Revision Id
>>> *.php = svn:eol-style=native;svn:keywords=Date Author Revision Id
>>> *.png = svn:mime-type=image/png
>>> *.sql = svn:eol-style=native;svn:keywords=Date Author Revision Id
>>> *.txt = svn:eol-style=native
>>> *.xml = svn:eol-style=native;svn:keywords=Date Author Revision Id
>>
>> eol-style=native? Does that mean, whoever checks out the sources will
>> get the eol-style of his machine? Sounds good, but for TYPO3 I think we
>> should stick to LF. All (good) Windows tools can read Unix-EOL anyway.
> 
> Yes, why bother with Unix-EOL when your tool may convert this on-the-fly
> when you commit? Just use your native EOL and let SVN handle whatever
> EOL style is needed on the repository or on other plateforms.

But why bother about local settings when the server can do that? Or do I
have a misunderstanding here when it comes to svn:eol-style? I think
this will force the line feeds to LF on the server (during a commit).

Masi