Hi, the company I'm working for plans to switch from our current commercial VCS, now I have the job to compare different tools (svn, git). Our clients run on Windows and probably our offices in foreign countries should work on our repository, too. Johannes Schindelin, 22.03.2009: > Disclaimer: Git for Windows is still in a state where I do _not_ recommend > using it unless you have the means to fix issues. Unlike the git.git > developer community, the msysGit team is heavily undermanned. > > Known issues I favor git, but I have to be objective and if there are serious issues, this will obviously influence the decision. Since the list below is not complete, I guess these are just the most serious issues, and then it doesn't sound too scary for the everyday use. Let me comment on them for our workflow: > - Some commands are not yet supported on Windows and excluded from the > installation; namely: git archimport, git cvsexportcommit, git > cvsimport, git cvsserver, git filter-branch, git instaweb, git > send-email, git shell. Not necessary. > - The Logitec QuickCam software can cause spurious crashes. See "Why does > make often crash creating a sh.exe.stackdump file when I try to compile > my source code?" on the MinGW Wiki > (http://www.mingw.org/wiki/Environment_issues) Not plugged-in. > - The Quick Launch icon will only be installed for the user running setup > (typically the Administrator). This is a technical restriction and will > not change. Never mind. > - Git Bash launched through the Explorer shell extension does not have the > git icon in its taskbar. This is a technical restriction and will not > change. Never mind. Probably I would be the only one using the CLI anyway. > - git send-mail does not work properly (Issue 27). Not necessary. > - curl uses $HOME/_netrc instead of $HOME/.netrc. Never mind. > - If you want to specify a different location for --upload-pack, you have > to start the absolute path with two slashes. Otherwise MSys will mangle > the path. Only for msysgit on the server side, right? Then, never mind. > - git and bash have serious problems with non-ASCII file names (Issue 80, > 108, 149, 159, 188). This may be a problem. > - If configured to use plink, you will have to connect with putty first, > as you cannot accept the host key due to the console window being > blocked (Issue 96). Just use OpenSSH? Problem in GUIs or only CLI? > - MinGW does not support IPv6 yet (Issue 182). Not necessary. > - When run from cmd.exe instead of Git Bash, some characters seem to be > "swallowed" from Git's output (Issue 192). Never mind. > - There are a few issues with ssh hanging (Issue 197), permission denied > on renaming pack files (mentioned in Issue 194), and spurious write > errors during rebase (Issue 200) that seem not to be reproducible on > most computers. OK, strange and not reproducible errors are a little bit scary. So, most of these issues I don't consider to be serious for us, but I guess the remaining "real" issues let you stay at your opinion, not to recommend using it, don't they? I suppose there are already people using msysgit productive at work, are these only people who know how to fix such problems? Regardless of git's Windows problems, another problem will probably be finding a decent GUI that suits my colleagues. Markus -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
