Line endings and tab conventions. about cuberite HOT 3 CLOSED

I agree with unix line-endings in the repository; after all, the window git clients can all be set to "checkout crlf, commit lf", which should be the default on everyone's machine.

As for tabs vs spaces, I've always used quite a strict rule, which I believe makes the most sense: indent by tabs, align by spaces, and don't mix both. Since I've authored quite a lot of code in MCServer, it would make sense to continue in this style.
What it means is that when it's a whitespace on the beginning of a line, it is a tab; when it's in the middle of a line, it's a space. The rationale behind is that everyone can set their tab width to whatever they want, and with that they'll adjust the indentation; but it won't break code alignment (sections of similar code aligned vertically, for example see the alignment in https://github.com/mc-server/MCServer/blob/master/source/BlockArea.cpp#L189 ).
For this to work, one needs to drop some bad habits, such as aligning multiline function calls to the parenthesis, and instead use indentation to show the levels (example in https://github.com/mc-server/MCServer/blob/master/source/BlockArea.cpp#L636 )

from cuberite.

Makes sense to me.

from cuberite.

I've changed the line endings, does everything seem good?

from cuberite.