Stephen Cuppett <cuppett <at> gmail.com> writes: > I actually have no problems with cygwin and find it works pretty well > with git repositories. Starting the xserver to run git-gui is pretty > annoying though. Windows-based development teams are going to expect > easy access to those kinds of tooling. Otherwise, the champion will > be pushing a type of workflow change that would hinder adoption anyway > and leave a sour taste for a long time. I have the version of git that came with cygwin, and I never have to run an X server to run git-gui or gitk. Personally, I can't imagine running git without cygwin. Course, I want my desktop to feel as much like unix as possible. My experience with git under cygwin has been excellent. My only gripe has to do with CRLF. The repository has everything checked in with dos line endings, I'd like to check everything out with unix line endings, and then check it back in with dos line endings. I hate seeing the ^M's everywhere. > In addition, performance is atrocious. In my particular case I have > an older P4 running F7 and a newer machine running Windows and cygwin. > On a pserver based cvsimport of a large, enterprise project, Linux > was able to generate the full history in 4 hours, cygwin took 3 and a > half days. When I sync up every now and then, typical times for > windows are 25 minutes and Linux is around 4. That should give you an > idea of what kind of multiplier we are talking about. Granted, the performance isn't equal to git running on a real unix, but compared to working with SVN under win32, I would say it performs quite well. - 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
