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

Re: SVN client 1.5.0 trouble on Windows

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Wed, 9 Jul 2008 14:16:07 -0500

On Jul 9, 2008, at 09:26, Robert Riebisch wrote:

> Philippe Andersson wrote:
>
>> I believe that these auto-props will be set only when you add a
>> new file
>> in the repository. They won't affect existing files, and certainly
>> not
>> in the context of an export. If the file "foo.dat" has CRLF line
>> endings
>> in the repository, I think that your only option is to simply
>> convert it
>
> According to the repository maintainer all files have UNIX-style LF
> line
> endings.
>
>> to "LF" line endings locally post export.
>
> I already do this as a work around, but I can't believe that SVN is
> that
> kind of "weird".

Subversion is not weird; it does exactly what it's told to do.

It sounds like whoever put the files into this repository has set the
"svn:eol-style" property of these files to "native". This means that
when checked out or exported on Linux or Mac OS X, the files will
have LF line endings, and when checked out or exported on Windows,
the files will have CRLF line endings. This is so that normal text
editors will be able to deal with the text files using the line
ending style that is usual for the operating system in question. You
showed that you're using Windows, so that's why you're getting CRLF
line endings.

If LF line endings are always desired for these files, even on
Windows, then the svn:eol-style property of these files should be set
to LF, not native.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-09 21:16:37 CEST

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

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