On Dec 28, 2005, at 13:48, Duncan Murdoch wrote:
> Ryan answered your questions, but I'd advise against using the eol-
> style property if you can. You will likely run into problems at
> some point, e.g. when using a Unix client to check out files but
> then editing them using a Windows editor, etc.
>
> I think you get fewer headaches in the long run by just getting
> your users used to using Unix-style line endings. Most Windows
> programming editors can do this; the only real problem comes with
> new files, on which those editors may default to CR-LF. But those
> will be very obvious the first time someone checks them out on
> Unix, and are easy to fix.
It sounds like you're actually advising against the use of the
"native" setting for the svn:eol-style property; I agree with that
advice. We have mostly Windows clients but a Linux server, and
because we develop PHP web sites our working copies are stored on the
Linux server, and are accessed from the Windows clients via SMB.
Sometimes we check out with TortoiseSVN on the Windows clients, and
sometimes we check out from the Linux command line, so a "native" eol-
style setting would be counterproductive for us. We do often still
have problems, though, with files getting committed with DOS
linefeeds, despite having instructed all developers on how to
configure their editors. Therefore, once we get our act together, we
will be converting all files to Unix newlines, setting the eol-style
property to LF and installing a pre-commit hook to enforce this policy.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 28 15:04:58 2005