You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Peter Hercek <pe...@syncad.com> on 2004/08/06 22:43:05 UTC

Re: "Inconsistent line-endings in source stream" error is not expressive enough

----- Original Message ----- 
From: "Ben Collins-Sussman" <su...@collab.net>
To: "Peter Hercek" <pe...@syncad.com>
Cc: <us...@subversion.tigris.org>
Sent: Thursday, July 29, 2004 15:03
Subject: Re: "Inconsistent line-endings in source stream" error is notexpressive enough


> On Wed, 2004-07-28 at 17:26, Peter Hercek wrote:
> 
> > There is a good reason for the error, but the problem is that
> >  when committing a lot of files, the files which actually have
> >  inconsitent line-endings are not listed in the error message.
> 
> I think this bug was fixed in 1.1.  I think.
> 

This was done with version 1.1.rc1 on both client and server:

Z:\temp\certificates>svn ci -m "[JHV]: [Ign] only a test of eol mismatch detection"
Sending        readme.txt
Transmitting file data .svn: Commit failed (details follow):

Z:\temp\certificates>svn --version -q
1.1.0-rc1

Z:\temp\certificates>

I think it is worse; in past it at least indicated that line endings are wrong.
Or did we something screw up when upgrading?


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: "Inconsistent line-endings in source stream" error is not expressive enough

Posted by Ben Collins-Sussman <su...@collab.net>.
On Fri, 2004-08-06 at 17:43, Peter Hercek wrote:

> Z:\temp\certificates>svn ci -m "[JHV]: [Ign] only a test of eol mismatch detection"
> Sending        readme.txt
> Transmitting file data .svn: Commit failed (details follow):
> 
> Z:\temp\certificates>svn --version -q
> 1.1.0-rc1
> 
> Z:\temp\certificates>
> 
> I think it is worse; in past it at least indicated that line endings are wrong.
> Or did we something screw up when upgrading?

Okay, I've finally fixed this problem on the /trunk code, r10546. 
Thanks for pointing this out.  We have better error messages now:


$ svn ci -m aoeu
Sending        dir2/file1
Adding         dir2/file4
Transmitting file data ..

subversion/libsvn_client/commit.c:764: (apr_err=135000)
svn: Commit failed (details follow):
subversion/libsvn_subr/subst.c:937: (apr_err=135000)
svn: File '/home/sussman/scratch/dir1/dir2/file4' has inconsistent newlines



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org