Hi, I'm currently evaluating DVCS for a project, and we're at a point where it comes down to either Mercurial or Git. Right now, I'm advocating for Git, while my co-workers like Mercurial, so I'd like to provide some good arguments in favor of git. Unfortunately, I'm not a git expert, so I hope I can get some help here ... First of all, what's the matter with git and Windows, is there some long-term commitment to make git work on Windows as well as on Linux? I'm using msysgit on Windows, and personally I'm happy with it, but my co-workers constantly nag that Mercurial has superior portability ... Mercurial's revision number system: With git, I get an SHA1 hash for every commit, but it's not possible to see whether Hash1 is newer than Hash2, while Mecurial also adds a running number to each commit. What's the rationale behind this decision for git, and is it possible to emulate Mercurial's behavior somehow? Integration into tools: We're using Trac currently, which also has a nice binding to Mercurial (well, obviously easy to do as Mercurial is written in Python, just as Trac itself), while the git support is in development and looks quite alpha'ish. Do you plan to make it easier to integrate git with other tools by providing bindings to other languages, or is this a low-priority issue? So far, my key arguments are that git is more robust (more projects using it, larger developer base), of course git's excellent performance and the much better support for SVN, which is important for us as we can slowly migrate from SVN->Git, while hgmercurial is still in the making (and Python's SVN->Hg switch is for instance waiting for it). Cheers, Anteru -- 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