Re: CRLF problems with Git on Win32
- From
- Johannes Schindelin <johannes.schindelin-mmb7mzphnfy@public.gmane.org>
- Date
- Jan 9, 2008, 20:50 UTC
- Message-ID
- <alpine.LSU.1.00.0801092047190.31053@racer.site>
- In-Reply-To
- <7vmyrehhkd.fsf-jO8aZxhGsIagbBziECNbOZn29agUkmeCHZ5vskTnxNA@public.gmane.org>
Hi,
On Wed, 9 Jan 2008, Junio C Hamano wrote:
Show 13 quoted lines
> Johannes Schindelin <Johannes.Schindelin-Mmb7MZpHnFY@public.gmane.org> 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.
Ciao, Dscho