Thanks Erik, it looks like it works.
I have to admit though that I have some difficulties understanding the
whole thing.
The manual says, and I quote,
"if a user on a Windows machine checks out a working copy that contains
a file with an svn:eol-style property set to native, that file will
contain CRLF EOL markers. A Unix user checking out a working copy which
contains the same file will see LF EOL markers in his copy of the file."
Which I'm sure it's true, but then why the error I experienced? I'm
puzzled :-)
Anyway, thanks for your help everybody, I think I'll stick with
svn:eol-style set to LF.
Giulio
> -----Original Message-----
> From: Erik Huelsmann [mailto:ehuels@gmail.com]
> Sent: 30 October 2006 15:01
> To: Giulio Troccoli
> Cc: Andy Levy; users@subversion.tigris.org
> Subject: Re: svn:eol-style issue
>
> On 10/30/06, Giulio Troccoli <Giulio.Troccoli@uk.linedata.com> wrote:
> > > In that case, setting the EOL style to LF is an option too, if VS
> > > handles those files correctly. I believe inconsistent EOLs will be
> > > forced iff your setting forces a particular style (which isn't
> > > 'native'). (I could be wrong, but have no time to check the
sources
> > > right now...)
> >
> > So you're saying that setting svn:eol-style to LF will force that
EOL
> > even when Visual Studio has added the CRLF. And if VS handles the LF
> > that we should be alright. Did I understand you?
>
> Yes, that's what I meant to say.
>
> bye,
>
> Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 30 16:46:21 2006