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

Re: Huge diff for one-line change in ASF repository

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sat, 15 Oct 2011 14:17:37 +0200

Ryan Schmidt wrote on Fri, Oct 14, 2011 at 19:37:44 -0500:
> On Oct 14, 2011, at 19:30, Daniel Shahaf wrote:
> > Ryan Schmidt wrote on Fri, Oct 14, 2011 at 19:18:44 -0500:
> >> When svn:eol-style is set to ANY value, the file is stored in the
> >> repository with LF line endings, and converted to the desired EOL
> >> style by the client on checkout or export (and converted by the client
> >> to LF line endings before being committed).
> >
> > Yeah, I thought so too, but when I try now with 1.7.0 I notice that
> > setting svn:eol-style to CRLF causes the versioned filesystem (read:
> > repository) to contain a file with CRLF set...
> >
> > And apparently it's the same with 1.6. I don't have any older builds
> > handy to test.
>
> Oh dear. I have apparently been repeating misinformation. The book says you're right:
>
> http://svnbook.red-bean.com/en/1.7/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style

Not sure where I got the idea that svn:eol-style files always use LF in
storage.

Probably some comment in the code referred to the repository-normal form
as "contracted keywords and LF linefeeds". This very question even came
up in Berlin at one point, but I don't really remember what I said there
and whether people corrected me...
Received on 2011-10-15 14:18:25 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.