On Friday 02 February 2007 09:30, Frodak wrote:
> I consider a file with mixed EOLs to be a binary file.
> If it was a text file then it wouldn't have mixed
> EOLs. When I run into this issue on a file I know is
> supposed to be text, I can easily fix the issue with
> sed or tr or have my editor save with unmixed EOLs.
>
> I don't think that this is something SVN needs. But
> if you guys do, by all means implement it.
>
> :-)
>
> Frodak
I was wondering if anyone can implement it. I've not done any work on
this project but believe that asking the user instead of aborting the
import would be trivial for a regular programmer already editing
subversion source. I will do it if it comes to that, but would be
useless if not widely accepted.
OK I see you have not followed the discussion from the beginning nor
the middle, or you have forgotten the issues. Go back and read
archives. For example yes they were not intentionally mixed (verified
text files but corrupted), and why make another tool that seeks out
the 7 out of 1000 which have been corrupt when svn already does that,
and no I'd prefer that svn tracked those changes, so I'd prefer a
slightly different approach then converting the line-ends first and
then importing the file. I'd not have imported my original text, now
would I?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 2 18:08:02 2007