问题
Cygwin's latest git, svn and git-svn combination is stuck at old versions that have numerous git-svn bugs. I'm considering just downloading the official windows version (warning: this will start the a download: http://git-scm.com/download/win ), putting that in my path, and calling those binaries from Cygwin. What are the downsides to this?
回答1:
Non-Cygwin Windows binaries won't be able to see Cygwin-style file paths. For example, your home directory might be /home/yourname as seen from Cygwin, but C:\cygwin\home\yourname as seen from Windows. Interactions between a Windows installation of git and the Unix-like Cygwin toolkit are likely to be very tricky.
Line endings may also be an issue.
An alternative is to build git from source.
回答2:
The official binary is Git for Windows (it says so on the download page).
The Git for Windows binary doesn't work very well with some cygwin tools.
For me, that means it doesn't work with mintty:
- No colors when running native windows shell application from mintty
- support for native console programs
git doesn't page or color output because it doesn't understand how to speak mintty's language.
I think the biggest problem is that I want to use cygwin as a complete suite of unix tools, but I get the impression that the goal of Git for Windows it to make Git a native Windows tool:
Finally, I came to the conclusion that it's too hard to make mintty work with msysgit. And IMHO, using mintty (although it's a great terminal) also is a step in the wrong direction in the sense that it introduces further tools and dependencies that are not Windows-native. Sebastian Schuberth (msysgit contributor)
It's a noble goal, but it doesn't meet my needs. Your mileage may vary.
Anecdotal: I haven't noticed problems with paths or line endings. However, Cygwin now provides git-2.1.1-1 so I'm giving up on msysgit.
来源：https://stackoverflow.com/questions/21027917/what-are-the-downsides-to-using-the-official-windows-git-binaries-from-cygwin