[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Interpretation of SVN MIME type property

From: Andreas Keil <rien_at_nurfuerspam.de>
Date: 2005-09-22 09:18:56 CEST

>>> [...]
>>>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").

You mean that line endings are never touched when committing a file? (Well,
if the docs are correct, at least for svn:eol-style=native this isn't true).
And what about files (without the svn:eol-style property) which SVN supposes
to contain text? Are they stored in a normalized format (with LF only as EOL
markers) or are they stored "as is", meaning a text file could have mixed
EOL markers in the repository?

>>>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>

I don't know what I could learn about proposed future keywords from the
docs. If I'm not wrong, we were talking about the idea of introducting a new
keyword which would tell SVN to stick with the original eol markers (which
cannot be specified by any of the existing values of svn:eol-style).

> [...]
>>>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.

OK, then I'm failing to locate the corresponding configuration in my WinXP
installation of TortoiseSVN.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 22 09:21:58 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.