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

Re: EOL?

From: Jan Danielsson <jan.danielsson_at_gmail.com>
Date: 2006-11-09 23:31:45 CET

Erik Huelsmann wrote:
>> I just started using Subversion. I come from a Perforce background,
>> but for a project I'm involved in now, we're going to use Subversion.
>> The installation hasn't been very smooth, but now I've got the server up
>> and running, and so I started trying it. It seems pretty ok, apart from
>> one major problem:
>>
>> The client doesn't convert source files to the platform's native
>> format, so when I check out the sources on my Windows system, some
>> applications get confused.
>>
>> I assume that it is supposed to do EOL-conversion seamlessly (just
>> like Perforce does), but on my system it doesn't .. so what have I done
>> wrong? :-)
>
> Hi Jan,
>
> I can advise the book as a whole, but your problem is addressed in
> this section:
> http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.special.eol-style

   I've read that, and frankly I don't know what to do with it. :-) I
kind of assumed that "native" was default, and since that wasn't
working, I assumed I was doing something wrong.

   I don't understand what this property thing is. Is it metadata
attached to each file? Because I don't want to have to explicitly set
native newline encoding in each file.

   As per suggestion in the docs, I tried setting
"enable-auto-props=yes" under "[miscellany]" in conf/svnserver.conf, and
then putting "* = svn:eol-style=native" under "[auto-props]" in the same
file, but the problem remains.

-- 
Kind Regards,
Jan Danielsson
Te audire non possum. Musa sapientum fixa est in aure.

Received on Thu Nov 9 23:32:35 2006

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