>> > 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?
>>
You can implement it but I don't think it will accepted. Subversion core
philosophy is that you don't change files during check-in. Since different
combinations of mixed line endings can generate the same file when converted
there will be some cases where a check-in will result in the working copy
being out of date. That means the subversion client will have to modify the
working copy file as well.
You can either agree or disagree with this I don't care. You can continue
the thread but don't bother to reply to me personally because I am filter
out further messages from this thread...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 2 20:40:36 2007