On Tue, Jan 24, 2012 at 8:44 PM, Richard Cavell <richardcavell_at_mail.com> wrote:
> What do you do if you're accessing the same filesystem from both Windows and
> UNIX? What line-ending method do you use for text files, and what do you
> put for svn:eol-style?
>
> Richard
I rely extensively on the default of *no* setting, referred to in
Subversion as not setting or blocking the "svn:eol" property. This
treats line endings as effectively binary data, preserved identically
no matter which platform you check out files on. If you need to work
with Windows line endings for source code on one system, and UNIX line
endings for source code on another, that's a locak system problem, not
properly a source control problem.
I'm afraid I've had real adventures when someone insisted on working
with TortoiseSVN with "svn:eol" set to "native", and thenm trying to
build perl scripts and Java source code on both Windows and Linux
systems in the same home directory. This led to madness....
> ----- Original Message -----
>
> From: Nico Kadel-Garcia
>
> Sent: 01/25/12 11:24 AM
>
> To: ANTOINE-PRAVEEN-JANVIER Joseph -EXT
>
> Subject: Re: Compatible with Microsoft Office and Internet Explorer
>
>
>
>
> On Tue, Jan 24, 2012 at 5:06 AM, ANTOINE-PRAVEEN-JANVIER Joseph -EXT
> <joseph.antoine-praveen-janvier-ext_at_alstom.com> wrote:
>>
>>
>>
>> Hello Support Team,
>>
>>
>>
>> We are the users of the Tortoise product and we need to know its
>> compatibility status with Microsoft application.
>>
>>
>>
>> Please let us know if the application is compatible with MS Office 2000,
>> MS Office 2010 and Internet Explorer (version 8).
>
>
> Hi there. This is the *subversion* mailing list, not the tortoisesvn mailing
> list, you should really ask over there. However, as a professional
> multi-platform systems admin and decades long integrator of source control,
> Microsoft operating systems, UNIX, and Linux since it came out, I I can tell
> you that it's very powerful and very effective. The recent updates to
> Subversion 1.7.x as its core have vastly improved its NTFS performance for
> Windows systems, and been all around good.
>
> The big booby trap I notice with all Windows/Subversion use is the
> understandable desire to use "native" end-of-line characters to swap text
> files gracefully between Linux, Windows, and MacOS. Don't do that: it can
> bite you *VERY* hard if you access the same network filesystem, such as a
> CIFS share, from each of those operating systems or with CygWin on Windows.
Received on 2012-01-25 03:18:16 CET