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

Re: converting from SVN to CVS

From: Spiro Trikaliotis <usenet-200901_at_spiro.trikaliotis.net>
Date: Mon, 26 Jan 2009 19:05:55 +0100


Paul Koning wrote:

>>>>>> "Kenneth" == Kenneth Goldman writes:

> Kenneth> - Newline conversion for Windows is automatic and cannot
> Kenneth> easily be turned off.
> I don't understand. If you have an svn:eol-style property it does
> what you ask for (which is vastly superior to what CVS offers).

No, it does not.

In CVS, a svn:eol-style=native file is opened in text mode, leaving the
handling of EOL to the OS (or the runtime environment), "doing just the
right thing".

With SVN, libapr determines an EOL style it believes might be correct,
and the file is written with that.

Unfortunately, libapr is wrong with Cygwin. This is a pity, as it
recognises Cygwin, but it neglects its details. (To be fair: The libapr
API does not have a way to handle this correctly.)

The problem with Cygwin is that there is not one "correct" EOL style,
but two: Cygwin supported LF and CR/LF - and it even supports mixed
configurations, in which some paths are LF, and some are CR/LF. libapr
handles this case statically - it always assumes LF: This is wrong for
many installations.

The easiest correct way: Open the file in text mode and believe the
runtime of Cygwin that it determines the correct style. Unfortunately,
SVN does not believe the runtime, but wants to handle it itself - which
is plain wrong, and a big bug.

CVS does this correctly.


Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-26 21:06:57 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.