From: Michael P. <mic...@gm...> - 2010-12-05 20:29:58
|
This one needs to be separate from the rest of my replies because of the quoting I'm doing here... Pete Batard wrote: >> As you pointed out earlier, I applied the safecrl settings advised by >> Peter when I started my branch (I remember getting my fingers slapped on >> this list for not using it). Sorry, my recollection (and my search of my email) indicates that you never used safecrlf. On 1/14, you said: >> "Currently I have AutoCrLf set in TortoiseGit. Can't set SafeCrLf as >> there seems to be a bug that prevents any commits when set (at least on >> Windows 7 x64)" On 1/22, Peter privately told me: >> git config core.safecrlf true On 1/28, Peter told Orin: >> Please git config core.autocrlf true; git config core.safecrlf true >> to try to avoid CRLF line endings in patches. On 1/28, you replied: >> Can't set safecrlf with TortoiseGit, as it prevents any pushes when set, >> but I don't think it's much of an issue as I'm only pushing text files. >> The safecrlf is the real only limitation I found with TortoiseGit as all >> the rest is working brilliantly, and seems very stable. On 4/27, you said: >> Also, it >> took me an awful long time to figure out that there was a bug when >> SafeCRLF was selected that prevented me to push. Only on 12/3 has Peter even hinted at a different story, and only after you revealed that you're still not using safecrlf: >> > my git/config for libusb is attached. [mkp note: it shows safecrlf=false] >> >> Hm. You set safecrlf explicitly. My git config --help doesn't say >> what the default is, but I don't think safecrlf=false can ever be >> harmful. But I think autocrlf=true explains why you need -text in >> your repo. >> It's only lately that Peter has been >> advocating different settings... That's not 100% clear to me. He does seem to have indicated safecrlf=false may not be harmful. That's about all I've seen. Do you have an email contradicting this? Michael |