At 09:19 2007-02-02, Hilco Wijbenga wrote:
>On 2/2/07, Jeff Smith <jsmith@robotronics.com> wrote:
>>Respecting text files does not mean, "oh, now there is no such thing
>>as a 'binary' file". I think it should default to binary treatment,
>>which it does. The only question is whether a "mixed line ending
>>style" text file is in fact a text file. How could anybody think that
>>it is not?
>
>So how is a file with mixed line endings supposed to be interpreted then?
>
>....\r
>TEXT\r\n
>....\n
>MORE\n\r
>
>Does that mean
>
>TEXT\r\n
>or
>TEXT\r
>\n
>
>and
>
>MORE\n\r
>or
>MORE\n
>\r
>
>What about \n\r\n? I can see three possible interpretations.
>
>I don't see how a file with mixed line endings could be interpreted
>without ambiguity.
that's almost irrelevant. There are lots of us here do DO see how it can be
>>If there is ANY file that requires special mixed EOL
>>styles for some purpose, then they are NOT TEXT FILES. So ask the
>>user!
>
>I do hope that doesn't mean Subversion is going to become interactive?
>A pre-commit script that simply refuses the commit if a "text" file
>has mixed line endings should work nicely.
>
>Cheers,
>Hilco
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
Victor A. Wagner Jr. http://rudbek.com
The five most dangerous words in the English language:
"There oughta be a law"
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 5 04:26:12 2007