TortoiseGIT

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]