Re: Why does import fail with autoprops ("inconsistent eol style")?

On Wed, Feb 23, 2011 at 6:20 AM, Stefan Sperling <stsp_at_elego.de> wrote:
[snip]
> Hmmm, I'm not following. Maybe there's a misunderstanding.

Looks like I'm the one that's not following. :-)

> The code does already override any inconsistent line endings for
> svn:eol-style values CR, CRLF, and LF. It just doesn't do so for 'native'.

Yep, you're right. I don't see why native was singled out in this case.

> So my question isn't about whether normalization should be done in the
> first place. It's about why it's only being done for the fixed values, and
> not for 'native' (which does translate to a fixed value in the repository).
>
> The feature isn't enabled by default anyway, so this isn't a question
> of modifying imported data by default. Users have to enable this in the
> config file before it has any effect.

In what config file? Do you mean enabling auto-props? I don't know
anyone who *doesn't* have it enabled. It's just too valuable. :-)

-John
Received on 2011-02-23 12:35:01 CET