On Tue, Jan 24, 2012 at 8:17 PM, Nico Kadel-Garcia <nkadel_at_gmail.com> wrote:
> 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.
No, it is a transport problem, and if you use a source control system
to transport text it should make it text as expected on each client.
> 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....
But the madness comes from not converting to the expected text form.
If you bypass that on purpose, do you preprocess every text file
before use on each system or restrict access to a small set of tools
that might work in spite of this input?
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2012-01-25 03:39:11 CET