Then the people who want to compile it rather than complain about it would have to go through an extra hoop to fix it again. They published it the right way.
That is an excellent point although I suspect your question is going to be answered in spades when people notice who the developer posting the code is.
Agreed, at least make sure it will still compile with line endings changed before submitting pull requests.
This builds with CodeWarrior 10 (from 1996) which is probably OK with non-Mac line endings, but there are other old Mac codebases on GitHub using older toolchains that require CR.
(i.e. Pararena 2: http://bslabs.net/2016/11/13/building-pararena/)
A PPC Mac running OS X 10.4 is basically the only way to work with both git and classic Mac dev environments, I'll be trying this out myself.
A year or two ago I built dropbear on Power MachTen, worked great and just needed a couple fixes to bring it back into compatibility with GCC 2.x.
Playing around with Professional MachTen (for 68k) is a real trip though. 4.3BSD, an even older GCC, and it implements virtual memory and protection by taking over the system memory manager. (You actually have to restart when quitting it)
It would be so cool to have something like MachTen on iOS, some people have tried but the restrictions on executable pages really restricts things.