On 7/13/2010 8:57 AM, Geoff Worboys wrote:
Les Mikesell wrote:
There are workarounds but you can't just expect things to
work in general and pretend it is normal. And some of
those workarounds may involve silently changing to the
preferred local line endings - and if anything but subversion
itself does that it becomes a change in every line when
committed, making diffs useless.
This may be true for some *nix systems/tools. But...
For most modern (Windows) development software it is not a
matter of "workarounds". They simply process the files and
accept whatever line endings they find. Good editors will
automatically switch between CRLF, LF and CR EOL modes
according to what they find. They don't change the file
(unless asked) they change their own mode operation.
If your developers all work with LF then there will be no
confusion and no need for workarounds. If anyone makes a
mistake and accidently commits a file with CRLF it is an
easy fix to resolve ... although most Windows software wont
care even if you don't bother to fix it.
If you have to worry about mistakes, you are doing workarounds. What
windows editor will create new files with LF endings by default?
--
Les Mikesell
lesmikes...@gmail.com
