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

Re: EOL marker handling was RE: converting from SVN to CVS

From: B Smith-Mannschott <bsmith.occs_at_gmail.com>
Date: Wed, 28 Jan 2009 19:31:08 +0100

On Wed, Jan 28, 2009 at 7:15 PM, Bob Archer <bob.archer_at_amsi.com> wrote:
>> This means that by default, Subversion doesn't pay any attention to
>> the type of end-of-line (EOL) markers used in your files.
> Are you are correct. I mis-took it to understand that eol-style:native
> was the default for all text files. But, I guess that is not correct. By
> default it doesn't do anything with EOL markers.

Subversions default behavior is to commit and restore your files as
they are: No conversion of line breaks.

Setting svn:eol-style to one of the values "native", "LF", "CRLF"
causes the appropriate EOL conversion on checkout.

>> What I'd really like to see is Subversion act if all text files have
>> svn:eol-style:native on by default, and either refuse to commit files
>> with mixed EOLs (as it does now) or fix them.
> It seems that you can get it to do this using enable-auto-props.
> However, it appears that this is [may be?] a client side config option.
> I'm not to sure though. The book isn't clear if the settings are client
> or server side. But, from reading it, it seems to be a server side
> option.

Yes, you can use auto-props on the client side to have the client set
svn:eol-style on new files when they are added. (You'll have to set it
yourself for files that have already been added.)

Here's an except of the relevant part of my ~/.subversion/config

enable-auto-props = yes
*.txt = svn:eol-style=native;svn:mime-type=text/plain
*.html = svn:eol-style=native;svn:mime-type=text/html

// Ben Smith-Mannschott
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-28 19:32:07 CET

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.