From: Laszlo Papp Date: Tue, 15 Dec 2009 15:41:04 GMT Subject: TortoiseGIT Message-ID: Hello, I had got a problem in the past with cr + lf between windows and linux client(maybe now too). I heard that from more experienced users I need to set autocrlf + safecrlf on windows, and core.autocrlf false on linux (which is the default), but If I set core.autocrlf true on linux too, it worked normally, after a git pull on windows I don't see any modified file that should be committed, not the case in core.autocrlf false. Could someone explain this habbit of git, please ? Everybody said I need to set autocrlf for false, but it doesn't work so, just with true on linux client, what do I do wrong ? It's okay now for me, because it works without any problem, I just don't understand the behaviour of it, and I don't know whether it will cause further problems. Thanks in advance! Best Regards, Laszlo Papp