4 ms·
I hope support for git continues to improve for Windows. Git Extensions is not bad, and works well for me, but I imagine it's still strange enough to put off de
by cicero 15y ago
I hope support for git continues to improve for Windows. Git Extensions is not bad, and works well for me, but I imagine it's still strange enough to put off developers that don't have nix experience. I love nix, but Windows is a reality in my life, so I am happy when I see good tools move to Windows.
- MatthewPhillips 15y agoYes, Windows developers with a very Windowy lineage of experience (something like DBase -> FoxPro -> Delphi/VB -> C#) don't get Unix tools at all. Someone could make a lot of money on a Windows git tool done right.
- bunderbunder 15y agoThere's a big part of me that wants to say, "It's already been done. It's called TortoiesHg." All the usual Mercurial command-line goodness, plus some very well-done Windows shell extensions. The biggest downside is that there just doesn't seem to be a good 3-way merge tool for Windows. Well, that and it doesn't enjoy Git's brand recognition.
- WayneDB 15y agoSmartGIT is not bad either and it includes a decent three way merge tool.
- lusr 15y agoGit Extensions + Git Source Control Provider for Visual Studio are great. Only annoying thing is that VS 2010 forces me to switch between SCC providers (Team System and Git) manually. (Anybody know if VS 11 resolves this? I stopped using the beta when it stopped being able to start my applications with debugging.)
- zxypoo 15y agoThere's some of us who work on JGit (http://eclipse.org/jgit/ http://eclipse.org/jgit/) which is used by many folks to get cross-platform Git support. The .NET community took things a step further by cross-compiling to C# via NGit (https://github.com/mono/ngit https://github.com/mono/ngit) to get solid Git support. Stepping back, it's a bit crazy to see these two different communities working together :)