[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: <kfogel_at_collab.net>
Date: 2005-02-08 23:03:12 CET

Ben Collins-Sussman <sussman@collab.net> writes:
> 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.

I think his objection is that it gets 20 minutes into the import, then
dies on one file, and after you fix that file, maybe it will go 40
minutes, then die on another file, and so on.

It would be more user-friendly to report *all* the problem files after
a single run. This might be complex to implement, but it's certainly
possible, and I wouldn't be averse to an enhancement issue being filed
about it. What do you think?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 8 23:21:11 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.