Christian Boos wrote:
Emmanuel Blot wrote:
Hi,
As I'm about to create new files for the notification subsystem
(following cboos recommendations), I'd like to double check the CR/LF
stuff:
Should I set the svn:eol-style property to 'native' on any new file ?
By the way, what's the advantage of having this property set to "native"?
I would pretty much prefer to have it set to "LF".
I think most editors are able to deal with "LF" end of lines.
OK, I've no idea of what's the situation on the Mac.
The problem with "native" is that an archive created on Linux will have
files with different eol than files from an archive created on Windows.
In the past, I had trouble creating patches that applied equally well
on .tar.gz and on .zip archives (see ticket #2028).
Switching from "native" to "LF" will only affect developers on the win32
platform since all other platforms already use "LF" natively.
So I guess "LF" might be a good choice if all commonly used
win32-editors can handle it.
How smart is the "eof-style:LF" mode anyway. What happens if I edit
a file on windows with a CRLF-editor and add a few new lines with CRLF
line endings in the middle of the file, will subversion automatically
replace them with LF-endings when I commit my changes?
Cheers,
Jonas
As an additionnal request, is there any objection to document these
kind of coding rules on TracDev/CodingStyle wiki page ?
What kind of coding rules, you mean the svn:eol-style ?
-- Christian
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
_______________________________________________
Trac-dev mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-dev
