git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Deciding between Git/Mercurial

From
MAMatthias Andree <matthias.andree@gmx.de>
Date
Sep 30, 2009, 11:09 UTC
Message-ID
<4AC33C56.8060202@gmx.de>
In-Reply-To
<h9nlhj$heq$1@ger.gmane.org>
Anteru schrieb:
> 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 ...

That tale is told all over, but that doesn't make it truer. I've never had issues getting a Cygwin version of git to work properly (haven't tried the msysgit or jgit variants, never felt the need), and integration went smooth.

With Mercurial, getting it integrated with a Windows-native Emacs (Cygwin emacs doesn't work for me but hangs on startup) was somewhat of an undertaking even with Cygwin's bash (rather than cmdproxy) underneath Emacs. It boiled down to building Mercurial with py2exe and create an installer and use the compiled hg.exe which I find starts rather slowly.

Show 5 quoted lines
> 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).

Yes, but beware of git-svn under Cygwin 1.5 - that works for svn+ssh:// URLs, but https:// or file:// don't work well because the underdocumented gazillion of dependencies piece of sh.. called apr does stupid things WRT temporary files since the Cygwin Subversion 1.6 days. Cygwin's Subversion 1.5 fared better.

I'm not sure about msysgit or jgit projects, but for Cygwin you'll definitely want to take the plunge and go for Cygwin 1.7 which is still in Beta (because that allows you to remove a file and create a file with the same name, which doesn't work with Cygwin 1.5).

Previous: Dilip MNext: Daniel Barkalow
Message 39 of 44 in “Deciding between Git/Mercurial”
  1. AnteruSep 27, 2009
  2. Robin RosenbergSep 27, 2009
  3. AnteruSep 27, 2009
  4. Alex RiesenSep 27, 2009
  5. Mark StrubergSep 27, 2009
  6. AnteruSep 27, 2009
  7. Alex RiesenSep 27, 2009
  8. Erik Faye-LundSep 27, 2009
  9. Pascal ObrySep 27, 2009
  10. Martin LanghoffOct 22, 2009
  11. Felipe ContrerasSep 28, 2009
  12. Matthieu MoySep 28, 2009
  13. Johannes SchindelinSep 28, 2009
  14. Felipe ContrerasSep 28, 2009
  15. Bruce StephensSep 28, 2009
  16. Matthias AndreeSep 30, 2009
  17. Dilip MSep 28, 2009
  18. Damien WyartSep 28, 2009
  19. Steven NoonanSep 28, 2009
  20. Sverre RabbelierSep 28, 2009
  21. Randal L. SchwartzSep 28, 2009
  22. Sverre RabbelierSep 29, 2009
  23. Mike RalphsonSep 29, 2009
  24. Matthieu MoySep 29, 2009
  25. Sverre RabbelierSep 29, 2009
  26. Jakub NarebskiSep 28, 2009
  27. Jakub NarebskiSep 29, 2009
  28. AnteruSep 29, 2009
  29. Leo RazoumovSep 29, 2009
  30. Jakub NarebskiSep 29, 2009
  31. Matthieu MoySep 29, 2009
  32. Leo RazoumovSep 30, 2009
  33. Björn SteinbrinkSep 30, 2009
  34. Andreas EricssonSep 30, 2009
  35. Jakub NarebskiSep 30, 2009
  36. Paolo BonziniSep 29, 2009
  37. Daniele SegatoSep 29, 2009
  38. Dilip MSep 29, 2009
  39. Matthias AndreeSep 30, 2009
  40. Daniel BarkalowSep 30, 2009
  41. Dilip MOct 22, 2009
  42. AnteruOct 22, 2009
  43. Dilip MOct 22, 2009
  44. AnteruOct 22, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.