[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: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-09-22 10:31:28 CEST

On Thu, 22 Sep 2005, Andreas Keil 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").
> 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).

Setting svn:eol-style is a request to make svn take care of the line
endings. If you don't set svn:eol-style, it won't modify the contents.

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

They are stored asis.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 22 10:32:48 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.