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

RE: Better failure message in case of inconsistent line-endings

From: Casper Hornstrup <chorns_at_users.sourceforge.net>
Date: 2004-11-26 23:07:53 CET

 

> -----Original Message-----
> From: Ben Collins-Sussman [mailto:sussman@collab.net]
> Sent: 26. november 2004 22:56
> To: Casper Hornstrup
> Cc: dev@subversion.tigris.org
> Subject: Re: Better failure message in case of inconsistent
> line-endings
>
>
> On Nov 26, 2004, at 1:31 PM, Casper Hornstrup wrote:
>
> > When committing a change with inconsistent line-endings, Subversion
> > complains like this:
> >
> > svn: Commit failed (details follow):
> > svn: Inconsistent line-endings in source stream
> >
> > Now you have to find all the problematic files yourself. This is
> > especially annoying when merging large changes from
> external sources.
> > Can you make Subversion print out the name of the file (or
> files) that
> > has inconsistent line-endings?
> >
>
> I think you're using a 1.0 client. This was fixed in the 1.1 client:
>
> $ svn ci -m "bloo"
> Sending monkey/README
> svn: Commit failed (details follow):
> svn: File '/Users/sussman/scratch/wc/monkey/README' has
> inconsistent newlines

You're right. Thanks.

Casper

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 26 23:12:28 2004

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