views:

326

answers:

6

It seems that both git and mercurial are rather Linux oriented. Which of them is more mature on windows?

+5  A: 

Mercurial has by far the most mature GUI tools for Windows. TortoiseHG is very good as well.

jsight
+3  A: 

Using my favorite search engine I find:

  1. VisualHG a mercurial plugin for VS
  2. HgSSCPackage another mercurial plugin for VS
  3. Git Extensions a git plugin for VS

I have not used any of these myself. I know Git is said to be less windows friendly but in my opinion this information is outdated furthermore this SO question might also be of interest. I guess this question really boils down to personal preference my suggestion would be to give each a try and see what you like best.

Bas Bossink
The HgSSCPackage plugin for Visual Studio just released version 1.2 and posted some impressive screenshots: http://bitbucket.org/zzsergant/hgsccpackage/wiki/ScreenShots
Martin Geisler
+8  A: 

Mercurial and TortoiseHG are IMHO the only option for Windows platform when speaking about distributed systems. git is not as mature under Windows and and probably never be. git originally was supported on Windows under cygwin and later msysgit was created using msys as base. There is of course TortoiseGit which seem to be nice GUI but as you see there is already some irregularities.

With Mercurial its just simpler. So for true experience consider TortoiseHG especially that they just released version 1.0 finally which has many goodies inside.

Michal Sznajder
msysgit works fine, the only thing I find missing is the lack of command line tab completion of `cmd`
hasen j
msysgit also lacks git-daemon.
jsight
there is also tortoisegit which has been suggested in a different answer. don't write off git just yet. however with spolsky's adoption of hg, it's quite likely that hg will become the dominant windows dvcs.
Mark Carey
+2  A: 

I've been using msysgit with the included bash (shell) without issues... And it comes with the tab-completion hasen-j is missing in cmd.

If you're a fan of Tortoise(SVN/HG/CVS/etc), there is also TortoiseGit.

Geoff
I use bash too on windows sometimes, but it doesn't integrate well with the rest of the windows environment. e.g. if you write a script that depends on paths having a driver letter such as `D:\ ` then it won't work in bash; and if you write it assuming `D:\ ` paths are in `/d/` then it won't work in `cmd` or any other bash that has `D:\ ` mapped somewhere else, like `/drives/d/` or whatever.
hasen j
True, I've used it (mostly) just with git; apart from the drive mapping, there's also the issue of .Net not being available (or something; I haven't really looked into it, but I had to open up cmd to run a .Net console app :-/ ).
Geoff
+4  A: 

Given the articles on SO I've been reading today, recommending that people turn off VCS integration plug-ins in Visual Studio, to make it run faster, I feel justified in keeping VCS operations out of the IDE.

Version 1.0 of TortoiseHg is getting very polished now, and it was perfectly stable and usable back at v0.5 when I started using it. It is definitely a mature product now, I'm just glad the developers have finally admitted it. *8')

Edit: I was looking at articles with tips for speeding up Visual studio. The only answer which I can find now which made this recommendation is this.

Mark Booth
Please refer me to the articles.
gkdm
I'm sure other people said similar things, possible in other questions, but since they were in comments, I now can't find them.
Mark Booth
Note that many VCS systems supply plugins because it is the **only** way to handle file renames. Another reason to love git :)
Benjol
+1  A: 

If you're looking for a strong integration with a DVCS inside Visual Studio: alt text

Check the full tutorial here: http://codicesoftware.blogspot.com/2010/03/distributed-development-for-windows.html

Plastic provides you with all the distributed stuff you need and is specifically designed to work on Windows (ok, it does Linux and Mac OS too, but it shines on Windows)

pablo