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

Re: EOL marker handling was RE: converting from SVN to CVS

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: Thu, 29 Jan 2009 20:53:26 +0100

On Thu, Jan 29, 2009 at 9:27 AM, Spiro Trikaliotis
<usenet-200901_at_spiro.trikaliotis.net> wrote:
> Hello,
> B Smith-Mannschott wrote:
>> On Wed, Jan 28, 2009 at 7:15 PM, Bob Archer <bob.archer_at_amsi.com> wrote:
>> Setting svn:eol-style to one of the values "native", "LF", "CRLF"
>> causes the appropriate EOL conversion on checkout.
> Not the "appropriate EOL conversion"; just what SVN *believes* to be
> appropriate, which is not always correct.
> But it seems the philosophy of SVN is to believe to know better than the
> system.

There is no "the system" here: if you open a file using Windows system
calls, there are no EOL translations. The same holds for Unix or any
other OS. In C, yes, if you use fopen() and friends, translation
happens. Subversion doesn't use those calls (for a whole slew of
reasons). So, we have our own eol translation, which translates to 1
eol string, depending on the platform detected (at compile time).

And, as I told you, we work on all operating systems we support. The
fact that cygwin doesn't work really is the problem of cygwin. Also,
the fact that you can compile Subversion on cygwin does not mean it's
an intended target to start with.

There's a very nice and well working native windows executable, which
took -and still takes- an extreme amount of additional work to be as
good as the *nix variant. Use it.




To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-29 20:54:21 CET

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

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