Andreas Keil wrote:
> Hi Marcus,
> you wrote:
>>lets assume we follow your idea:
>>1. svn allows you to set svn:eol-style only on text files.
>>2. a user adds a pdf file. the current heuristic says text. yes that can
>>happen with pdf.
>
> Well, but then it's already corrupted on the server after the first commit,
> right?
Wrong. All files are stored in the same way and their bytes are not changed
unless a specific change is requested on the client side (e.g. by setting
"svn:eol-style" or "svn:keywords").
>>3. the user sets eol-style
>
> To sth. like "binary", "original", or "keep" I assume.
Please read about it in the book:
<http://svnbook.red-bean.com/en/1.1/ch07s02.html#svn-ch-7-sect-2.3.5>
[...]
>>there is already a hard coded list for that. if you move that list into
>>$HOME/.subversion/config you configure it at
>>runtime. enough? once we get pushing server side configs to the client
>>this process can be optimized for large teams.
>
> You are talking about the SVN server, not a client, rigth? Unfortunately, I
> don't have access to the server and therefore cannot look for this
> hard-coded configuration :-(
He's talking about a hard-coded list in the client software itself, and
proposing that we move it to the existing client-side configuration file, and
further hoping that one day it will be possible to configure it on the server
too. Please read about configuration in the book.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 20 17:48:13 2005