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 ? -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
