On Wed, 25 Jul 2007, Dmitry Kakurin wrote: > How serious are you guys about Windows support? > I'm talking fully-functional port, not Cygwin. > I did a lot of searching for a new SCM to switch to (from Perforce). > And Git is my #1 choice. I love it's internals design and it's > expressive power. I've also tested git-p4 and it has worked like a > charm with my depot (with few tweaks that I may contribute later). > But I do all my work on Windows so I need Git-For-Windows-Done-Right :-). > The current mingw port is not there yet. > > Transition to the new SCM must happen now, so basically I have 2 choices: > 1. Survive for a few months with the current CygWin port of Git > knowing that Windows support is coming > 2. Use another SCM (#2 is Mercurial, #3 is Monotone) > > I'd realy love to do #1, but I need to know how long do I have to wait. If the issue is the shell scripts, replacing those with C code is coming along nicely; there's a big section (fetch and everything it uses) which is ready to go after 1.5.3 comes out, and I believe a number of the other core parts are being taken care of in the same sort of time frame by the GSoC people. I've also been working on reducing the fork/exec usage, if that's the issue, but I'm not sure how much of that is left to do or how long it will take. (Personally, I don't touch windows at all, but I have been working on fixing things that seem to be problems for porting to windows, which may be relevant) -Daniel *This .sig left intentionally blank* - 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
