[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn diff and native eol style

From: Branko Čibej <brane_at_xbc.nu>
Date: 2004-04-04 18:47:46 CEST

Tobias Ringstrom wrote:

> Branko Čibej wrote:
>> I don't think we should convert at all. If the files differ only in the
>> EOL style, I think diff should show that (unless given an ignore-eol or
>> ighore-whitespace option).
> When the eol style is native, the text base has LF endings, and the WC
> has CRNL line endings on Win32, so some conversion must be made.
> Remotely accessed files also use LF only when svn:eol is native.

Some conversions must be made anyway, to account for keywords and such.
This means that the text base has to be converted to native format.

For example, currently if your editor inserts different EOL chars than
those already used by the file, "svn diff" won't tell you about that,
but "svn ci" _will_ store the wrong delimiters (of course unless
svn:eol-style is native).

It's a can of worms, and situations like this make me lean towards
agreeing with ghudson about the evilness of newline conversion. :-)
Sadly, we have to live with it. And silently curse Windows that got its
convention from DOS that got it from CP/M that got it -- probably --
from teletype transmission standards... and some research would probably
show it all stems from some convention used by Summerian scribes, or
something :-\

Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 4 18:46:29 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.