Hi, I just came across the line ending issues when working with Git where the OS of the committers is not unique.
In [1] is explained that you can handle this by local Git configuration (core.autocrlf) and/or via .gitattributes directly in the repository. Adding the .gitattributes should handle things correctly even if the local Git configuration property is missing. At least I understand it that way. Wouldn't it make sense then to add such a .gitattributes to Nebula too? Rejecting contributions because of wrong line endings when it can be handled automatically feels wrong. What do you think? Greez, Dirk [1] https://help.github.com/articles/dealing-with-line-endings
_______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
