Re: mingw, windows, crlf/lf, and git
- From
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
- Date
- Feb 12, 2007, 00:14 UTC
- Message-ID
- <200702120114.21477.robin.rosenberg.lists@dewire.com>
- In-Reply-To
- <45CFA30C.6030202@verizon.net>
måndag 12 februari 2007 00:13 skrev Mark Levedahl:
Show 14 quoted lines
> The recent threads on a mingw git port are explicit in the intent to > provide a Windows native git. I believe there is a fundamental conflict > here with the position, clearly stated by Linus, that git does not alter > content in any way. Windows suffers the curse of DOS line endings (\r\n > vs \n), and a true port to Windows *must* allow for \r\n and \n to be > semantically the same thing as most large projects end up with a mixture > of such files and/or are targeting cross-platform capabilities. The > major competing solutions git seeks to supplant (cvs, cvsnt, svn, hg) > have capability to recognize "text" files and transparently replace \r\n > with \n on input, the reverse on output, and ignore all such differences > on diff operations. To be relevant on native Windows, git must do the > same. Otherwise, git will be deemed "too wierd" and dismissed in favor > of a tool "that works." >
As of today git is a posix tool simply because it's not fully ported to other enviromnents. I brought this up quite a time ago, and didn't face heavy artillery then, and wouldn't today either. The code is still missing though. I didn't write it then, because it's my #1 priority and nobody else did. Linus even did a rough scetch, but that's it.
I guess git will get this feature when someone does the code for it.
-- robin