[ https://issues.apache.org/jira/browse/UIMA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward Epstein updated UIMA-2311: --------------------------------- Fix Version/s: 3.0.0C > wrong or no svn:eol-style set on many files in uimacpp > ------------------------------------------------------ > > Key: UIMA-2311 > URL: https://issues.apache.org/jira/browse/UIMA-2311 > Project: UIMA > Issue Type: Improvement > Components: C++ Framework > Reporter: Marshall Schor > Assignee: Edward Epstein > Priority: Minor > Fix For: 3.0.0C > > > Files that developers edit with text editors are usually marked with the svn > property svn:eol-style native. This insures that when they are checked out, > the line endings are converted to the client's style of line endings, and > when changes are checked in, the line endings are normalized, so that lines > which are not changed don't appear in the diff. > Without this, we have seen cases where a file is stored with some line ending > in SVN, checked out onto a machine with different default line endings, > edited and saved (causing the line-endings to be changed to that machine's > default style), and then committed. The commit shows as if every line has > been changed, whereas the real change might have been just a few lines. This > makes for difficult reviewing of the commits, of course. > I found many examples in the uimacpp project where the svn:eol-style is > missing, or where it was set to LF (which might be alright, but native is > probably safer). > Committers: It is highly recommended that you can set up your SVN to > automatically tag "new" files with the right svn:eol-style, by following the > instructions here: http://www.apache.org/dev/svn-eol-style.txt -- This message was sent by Atlassian Jira (v8.3.4#803005)