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

Re: Changing the behaviour of eol-style "native"

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Sat, 09 Jan 2010 20:27:39 +0100

On 09.01.2010 20:22, Simon Large wrote:
> 2010/1/9 Andy Levy<andy.levy_at_gmail.com>:
>> On Sat, Jan 9, 2010 at 13:29, Stu Redman<sturedman_at_gmx.net> wrote:
>>> Hi,
>>> I'm working on a cross platform project where most files have the
>>> attribute eol-style "native". I'm using TSVN on Windows and replicate
>>> the files to a Linux machine.
>>> Now TSVN checks out "native" files as CRLF, but many files (like shell
>>> scripts) do not work on Linux in this mode. What I'd like to do is
>>> switch the "native" mode on TSVN so that "native" files get checked out
>>> in LF format. Is there an option in TSVN for this? If not - is it
>>> possible to add this as a new feature?
>> "Native' is exactly that - native to the OS which checked out the
>> working copy. Working copies are not meant to be shared between users
>> or operating systems.
>> Check out a separate WC on the Linux machine, or change your eol-style
>> to LF. But this is really busy work - any text editor worth using in
>> 2010, on any platform, should handle any EOL style perfectly fine, and
>> programs which read text files for processing should be coded
>> appropriately to handle any EOL style as well; it's not like CRLF line
>> endings just appeared yesterday.
> Editors should be OK, but I know from experience that shell scripts
> and makefiles that have CRLF line endings just fail with an unhelpful
> error message. Using svn:eol-style=LF for those files that need it is
> an easy solution.
> I have to admit that I have done exactly this. We had a project a
> while back which could only be built on Linux, and we are a Windows
> shop. We had a single Linux server set up to share the user home
> directories using SAMBA. I could then map the Linux share in Windows,
> checkout a working copy using TSVN and edit using my familiar windows
> editor. The only part that required Linux was the build itself, which
> could be done using a PuTTY session. Since I never used a Linux svn
> client, there was no WC compatibility issue.

You should never ever share a working copy between OS! Always check out
a separate working copy.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-01-09 20:27:54 CET

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

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