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

Re: svn:eol-style of 'native' - avoiding corrupting binary files

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Fri, 15 Feb 2008 21:31:51 +0000

On 15/02/2008, Stephen Dewey <stepheneliotdewey_at_gmail.com> wrote:
> I'm assuming that if we set a binary file (e.g. .jpg) to have a
> property of svn:eol-style=native, downloading it will result in file
> corruption since certain characters will be identified as newlines and
> changed although they are not newlines. Am I right in that assumption?


> Is svn:eol-style=native only safe for ASCII files, or just for all
> human-readable files (e.g. UTF-8 character strings), or something
> else?

Anything where you want the line endings to be CR-LF on Windows and LF
on *nix. Usually that is any form of plain text file. If you only ever
use Windows, you don't have to use eol-style at all. The only reason
we use it on this project is that the server which generates the
post-commit emails runs on Linux and treats CR-LF as LF-LF and gives
us double-spaced emails.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-02-15 22:32:02 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

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