Les Mikesell wrote:
> Duncan Murdoch wrote:
>
>
>> svn is for revision management. It's nice that it can handle the common
>> cases of text format translation, but that's not its main goal, and if
>> the simple thing it does doesn't work for you, turn it off.
>>
>
> It isn't "nice" that it can handle text - it is an absolute requirement
> for a cross-platform tool that tracks differences to understand that
> text is different across platforms. Personally I think CVS had it right
> in making text handling the default and binary the exception but I
> understand the reasoning for the change.
>
I guess we'll just have to disagree. I think it's an absolute
requirement that svn shouldn't change the file content. If the file is
text, and the transformation to native eol style is clear and
reversible, then that's possible even with eol translation. If the file
has mixed eols, I don't see a reasonable rule for what it should do:
you want native eols on your platform, but you're starting with a file
that doesn't have them. It would be unacceptable (to me) to commit a
file then check it out and get something different. If the user
declares a file to be text and wants "native" eol
handling, then the file should be a file where that's possible, or svn
should tell the user to figure out what he's really asking for.
> What would be "nice" would be for it to be more forgiving about input
> styles and to have options to specify that you'd prefer your output in a
> different style than native for the client where you happen to execute
> the command.
>
>
There are lots of tools to convert files. I don't want svn to become
one of those, except to the minimal extent possible.
Duncan Murdoch
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 2 02:17:13 2007