On Thu, Jan 29, 2009 at 9:53 PM, Erik Huelsmann <ehuels_at_gmail.com> wrote:
> On Thu, Jan 29, 2009 at 9:27 AM, Spiro Trikaliotis
> <usenet-200901_at_spiro.trikaliotis.net> 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
> 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.
I found this in the help for svn export:
--native-eol ARG : use a different EOL marker than the standard
system marker for files with the svn:eol-style
property set to 'native'.
ARG may be one of 'LF', 'CR', 'CRLF'
Wouldn't it be a good idea to add this option to the checkout command as well?
I have a usecase where I only have access to the repository from a
Windows machine, but would like to do changes from Linux. Checking out
on Windows, moving the WC on a USB-stick, modifying in Linux, moving
back and committing from Windows might solve my problem.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-15 06:58:20 CEST