From: Steffen Prohaska Date: Wed, 09 Jan 2008 21:03:35 GMT Subject: Re: CRLF problems with Git on Win32 Message-ID: <41A4384C-1D8D-4111-8C2C-90B6E8F6364C@zib.de> In-Reply-To: On Jan 9, 2008, at 9:50 PM, Johannes Schindelin wrote: > Hi, > > On Wed, 9 Jan 2008, Junio C Hamano wrote: > >> Johannes Schindelin writes: >> >>> Junio wrote: >>> >>>> Perhaps we can do something similar to core.filemode? Create a >>>> file >>>> that we would need to create anyway in "text" mode, and read it >>>> back >>>> in "binary" mode to see what stdio did? >>> >>> The problem is that MinGW behaves sanely, i.e. it does not output >>> CRLF >>> but only LF. >> >> Won't that behaviour be viewed rather as "insanely" from majority of >> Windows users? > > I think the truth is that CRLF was a mistake. Nobody wants to take > the > blame for it, obviously, but more and more Windows tools just grok > LF-only > text. > > The question is: what to do with those that cannot grok LF-only > text. I > imagine that the best compromise for now would be to have > crlf=true, with > poor souls like Steffen having to set the gitattributes accordingly. I could live with that but unfortunately this alone does not solve all of the real-world problems happening during cross- platform development. At least the problem of code copied from Windows to Unix and committed there should be addressed, too. Maybe the default on Unix should be crlf=input? I'm wondering what Linux developer would say about this? I am against changing the default of msysgit now. First I'd like to wait how the "crlf=safe" discussion evolves. Steffen