CRLF issues on checkout (was Re: Gnucash 2.5/6 - jqplot)

[Mike Alexander]

--On February 23, 2013 5:07:47 PM +0100 Christian Stimming 
<christian at cstimming.de> wrote:

> I think the easiest way out here (as long as we're still using SVN)
> is to set  the per-file SVN property svn:eol-style to some fixed
> value (here: LF). This  ensures the file get one canonical set of eol
> markers.
>
> However, setting this property requires a client-side action: Either
> the file  ~/.subversion/config needs some manual changes as described
> here
>
>
> http://stackoverflow.com/questions/5671406/force-svneol-style-native-
> on- the-server
>
> which sets the property at the initial checkin of each file, or we
> need to do  one additional SVN commit to set that property, which
> I've just done in  r22809.
>
> Note: For most of our *.h / *.c files I've also done this manually in
> e.g.  r20217 or r18959, which explains why we didn't have any trouble
> with those  files and line endings. I strongly suggest for every
> developer to modify one's  own ~/.subversion/config to set
> svn:eol-style=LF for *.h, *.c so that we  continue with a consistent
> setting of the line endings.

Do you really want to use LF for eol-style for these file types?  I 
would think that "native" would work better.  That's what I've been 
using for years on various SVN projects and it seems to work well.  I 
don't work on Windows much anymore, but I used to and often worked on 
the same file on both systems.  "Native" is also what the stackoverflow 
article you mention suggests.  If you specify this eol format then the 
local file will be in the native format but the repository version will 
always be with LF line endings.

For a discussion of the eol-style property see

<http://svnbook.red-bean.com/en/1.7/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style>.

             Mike