2011/11/21 John Arthorne
<John_Arthorne@xxxxxxxxxx>
After long struggles in the Eclipse top-level
project we settled on the following approach:
http://wiki.eclipse.org/Platform-releng/Git_Workflows#Dealing_with_line_terminators
See the referenced mailing list discussions
for more background on the reason to avoid relying on autocrlf. Note to
clean up a mess you can also do the following:
- Select multiple projects in Eclipse
- File > Convert Line Delimiters
to > Unix.
- Commit/push the changes
Eclipse's built in detection of binary
vs. text files is quite good - at least much better than Git will do out
of the box.
Resorting to git-filter-branch is quite
a drastic measure. This destroys all existing commit records and can cause
major problems if all team members don't correctly re-clone afterwards.
That seems like a last resort option, unless you have only done the
conversion to Git very recently and aren't worried about starting over.
AFAIK JGit and EGit currently only support core.autocrlf=false
