On Sat, 25 Oct 2014, Ryan Ollos wrote:
The case willneed to be made why we should favor one particular set of line endings.
Because "\n" is the standard for all operating systems with only one exception. And it is BTW also the way how the files are stored in the versioning system.
Supposing "\r\n" causes problems on Unix (I don't know, I've never noticed any problems), does "\n" not cause any problems on Windows?
Neither does \r\n cause major problems under Linux, nor does \n cause problems for Windows.
But e.g. you will get conversion issues for any patches from Unix users and if somebody uses the release files and copies these into SVN results will be \r\n checkins for UNIX SVNs, diffs and patch files don't work without conversion first, ...
As said. It is simply UGLY and non-standard. Ciao -- http://www.dstoecker.eu/ (PGP key available) -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
