{"thread":{"id":"21960","subject":"TortoiseGIT","startedAt":"2009-12-15T15:41:04Z","lastAt":"2009-12-16T06:26:22Z","messageCount":2,"participants":["Laszlo Papp","Frank Li"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"129947","messageId":"a362e8010912150741x2c39c01bh1f64e669726dafab@mail.gmail.com","threadId":"21960","inReplyTo":null,"subject":"TortoiseGIT","fromName":"Laszlo Papp","fromEmail":"djszapi@archlinux.us","sentAt":"2009-12-15T15:41:04Z","receivedAt":"2009-12-15T15:41:04Z","isPatch":false,"sender":{"key":"djszapi@archlinux.us","avatar":null},"body":"Hello,\n\nI had got a problem in the past with cr + lf between windows and linux\nclient(maybe now too).\nI heard that from more experienced users I need to set autocrlf +\nsafecrlf on windows, and core.autocrlf false on linux (which is the\ndefault), but If I set core.autocrlf true on linux too, it worked\nnormally, after a git pull on windows I don't see any modified file\nthat should be committed, not the case in core.autocrlf false.\n\nCould someone explain this habbit of git, please ?\n\nEverybody said I need to set autocrlf for false, but it doesn't work\nso, just with true on linux client, what do I do wrong ?\nIt's okay now for me, because it works without any problem, I just\ndon't understand the behaviour of it, and I don't know whether it will\ncause further problems.\n\nThanks in advance!\n\nBest Regards,\nLaszlo Papp\n"},{"id":"129983","messageId":"1976ea660912152226r63f549d0oc64f93eaf0d4abe2@mail.gmail.com","threadId":"21960","inReplyTo":"a362e8010912150741x2c39c01bh1f64e669726dafab@mail.gmail.com","subject":"Re: TortoiseGIT","fromName":"Frank Li","fromEmail":"lznuaa@gmail.com","sentAt":"2009-12-16T06:26:22Z","receivedAt":"2009-12-16T06:26:22Z","isPatch":false,"sender":{"key":"lznuaa@gmail.com","avatar":"https://avatars.githubusercontent.com/u/40642?v=4"},"body":"You keep cr+lf on/off on whole develop cycle.  Avoid change it during\ndeveloping.\nAfter change cr+lf setting, I perfer you remove all work copy and\nrecheckout all.\n\nbest regards\nFrank Li\n\n\n2009/12/15 Laszlo Papp <djszapi@archlinux.us>:\n> Hello,\n>\n> I had got a problem in the past with cr + lf between windows and linux\n> client(maybe now too).\n> I heard that from more experienced users I need to set autocrlf +\n> safecrlf on windows, and core.autocrlf false on linux (which is the\n> default), but If I set core.autocrlf true on linux too, it worked\n> normally, after a git pull on windows I don't see any modified file\n> that should be committed, not the case in core.autocrlf false.\n>\n> Could someone explain this habbit of git, please ?\n>\n> Everybody said I need to set autocrlf for false, but it doesn't work\n> so, just with true on linux client, what do I do wrong ?\n> It's okay now for me, because it works without any problem, I just\n> don't understand the behaviour of it, and I don't know whether it will\n> cause further problems.\n>\n> Thanks in advance!\n>\n> Best Regards,\n> Laszlo Papp\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n>\n"}]}