Re: "Inconsistent newlines": A clue

On Tue, 8 Feb 2005, Ben Collins-Sussman wrote:

> > 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?
> >
>
> I'm not sure I understand the proposal. One runs 'svn import', and
> then 20 minutes in, you see a message like
>
> svn: file X has inconsistent newlines
> svn: this commit will fail, but continuing to search for other such
> files...
>
> ?
>
> Perhaps a better solution is a tool to go into contrib/ which will scan
> a directory for files with this problem. It can be used as a
> "pre-flight" check before large imports.
>

Yes, that's an excellent suggestion.

And perhaps I should be the one to write it. I just found out Monday my
contract is being terminated, so I should have hte time ;)

I see that a fair number of contrib programs are done in Perl, so I'll us
e that.

How does one add something to contrib, once written?

----------------------------------------------------------------------------
DDDD David Kramer david_at_thekramers.net http://thekramers.net
DK KD
DKK D "You can build a throne out of bayonets,
DK KD but you can't sit on it for very long.
DDDD - Boris Yeltsin

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 9 19:11:39 2005