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

Johannes Schindelin wrote:

Whatever is done, it needs to be robust to the notion that people will fail to set the correct file type somewhere. Current cvsnt is fairly good at autodetecting and setting text vs binary file type, and enforces this across all platforms, so things don't go awry too often. It is in my experience more reliable than subversion, which basically relies upon file extensions mapping to mime types to identify content. All of which is a very much too low standard of accuracy for a version control system: I lost many files per year due to the above nonsense, so I worry about trying to create a very general transform solution and not making it really, really failsafe. Having projects define individual globbing patterns is good, double checking the content for sanity is an absolute must, but I don't think that is enough. I suspect the solution should include round-trip conversion when creating blobs to assure that the input can be exactly reconstructed by the inverse transformation (and therefore possibly rejecting input with mixed line endings). A similar check could be applied on checkout.

Perhaps I'm too paranoid, but I've been burnt way too many times by text/binary mode stuff to let this part be trivialized. Maybe it only gets enabled by core.ImReallyParanoid, but I want that option.

Mark