Re: mingw, windows, crlf/lf, and git

[Nicolas Pitre <nico@cam.org>]

On Tue, 13 Feb 2007, Sam Ravnborg wrote:

> This whole auto CRLF things seems to deal with DOS issues that I personally
> have not encountered since looong time ago.

Maybe you didn't share a work environment with Windows users since 
looong time ago.

> Granted notepad in Windows does not understand UNIX files but that a bug
> in notepad and everyone knows that wordpad can be used.
> 
> I wonder what we are really trying to address here. Or in other words
> could the original poster maybe tell what Windows IDE's that does
> not handle UNIX files properly?

Windows IDE's can _create_files.  Those files will be CRLF infected.

Also some of them read UNIX files just fine but they will use CRLF to 
end new added lines despite the rest of the file using only LF.

> core git today should not care about CRLF as opposed to LF end-of-line
> as long as the end-of-line is consistent - correct?

Consistency won't come alone if not enforced in some way.

> So defaulting to autoCRLF in Windows/DOS environments was maybe
> sane 10 years ago but today that seems to be the wrong thing to do.
> For certain project the option could be useful if the tool-set in
> the project *requires* CRLF, but if the toolset like all modern toolset
> supports both CRLF and LF then git better avoid changing end-of-line marker.

Rather git better enforce consistency otherwise it'll be only a mix of 
possible combination as soon as Windows and UNIX users work on the same 
project.


Nicolas