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

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

From: Stefan Sperling <stsp_at_elego.de>
Date: Wed, 23 Feb 2011 11:47:35 +0100

On Wed, Feb 23, 2011 at 04:56:03AM -0500, John Szakmeister wrote:
> On Tue, Feb 22, 2011 at 1:35 PM, Stefan Sperling <stsp_at_elego.de> wrote:
> > When trying to 'svn import' files that have a mixed eol style,
> > and at the same time using autoprops to set an svn:eol-style property
> > with value 'native' on this file, svn import aborts with an "Inconsistent
> > line ending style" error. Is there any specific reason for this?
> > Can't we just normalize the file to LF (i.e. the repository normal form)?
>
> I think it was probably part of Subversion's "do no harm" decision
> policy. If the type of the file was actually binary, and the
> autoprops changed it, then the file would be corrupted from the
> beginning.

If that's the reasoning then why is it normalising the data
for svn:eol-style with values other than 'native'?

> > It's a nuisance when migrating data from other version control systems
> > into Subversion, especially if a lot of files are affected and the old
> > system doesn't support handling files with mixed newlines in a smart way.
> > To apply autoprops in this case another checkout/svn_apply_autoprops/commit
> > cycle is needed, or manual translation of the affected files is required
> > before running the import, both of which can take a long time with large
> > data sets.
>
> Yep, I agree.
>
> [snip]

Thanks. I'll start working on a patch.

>
> -John
Received on 2011-02-23 11:48:18 CET

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

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