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

Re: "Inconsistent newlines": A clue

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-02-08 18:48:06 CET

On Feb 8, 2005, at 11:29 AM, David Kramer wrote:

> I'm trying to svn import a big mess o files. We have the autoprops
> eol-style native set (see previous message).
> When I do the import, I get that message on some of the files, then it
> dies. This is REALLY bad behavior in my eyes, because each try takes
> over
> 20 minutes, and I have not found a reliable mechanism for identifying
> files it will barf on. I would much rather it warn about that file and
> move on. Why does it care anyway?

If you set 'svn:eol-style = native' on a file (which you're probably
doing with auto-props), and then try to commit the file, svn will barf
if it discovers inconsistent line endings.

Why? Because if it converted the line endings to all LF or all CRLF,
the conversion would be lossy. There's no way to get the original file
back. Subversion refuses to lose data. Therefore, it barfs and
demands that you fix the inconsistent line endings yourself.

Be thankful that it's doing this, not angry.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 8 18:51:22 2005

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.