The following solved the problem:
git config --global core.autocrlf false
So it wasn't a Swagger problem at all, but introduced by a gi pull.
Swagger codegen obviously uses LF in every case.
Anyway, and just out of curiosity:
Is there an easy way to tell Swagger codegen, whether to use LF or CRLF ?