Hi Hannes, On Tue, 24 Oct 2017, Johannes Sixt wrote: > Am 24.10.2017 um 19:48 schrieb Lars Schneider: > > I've migrated a large repo (110k+ files) with a lot of history (177k > > commits) > > and a lot of users (200+) to Git. Unfortunately, all text files in the index > > of the repo have CRLF line endings. In general this seems not to be a > > problem > > as the project is developed exclusively on Windows. > > > > However, I wonder if there are any "hidden consequences" of this setup? > > I've been working on a project with CRLF in every source file for a decade > now. It's C++ source, and it isn't even Windows-only: when checked out on > Linux, there are CRs in the files, with no bad consequences so far. GCC is > happy with them. I envy you for the blessing of such a clean C++ source that you do not have any, say, Unix shell script in it. Try this, and weep: $ printf 'echo \\\r\n\t123\r\n' >a1 $ sh a1 a1: 2: a1: 123: not found For the same reason (Unix shell not handling CR/LF gracefull), I went through that painful work that finally landed as 00ddc9d13ca (Fix build with core.autocrlf=true, 2017-05-09). Ciao, Dscho
