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

Re: Deciding between Git/Mercurial

From
DSDaniele Segato <daniele.bilug@gmail.com>
Date
Sep 29, 2009, 08:44 UTC
Message-ID
<9accb4400909290144t1363b5c6t8886bfa01e486c94@mail.gmail.com>
In-Reply-To
<h9nlhj$heq$1@ger.gmane.org>

On Sun, Sep 27, 2009 at 2:24 PM, Anteru <newsgroups@catchall.shelter13.net> wrote:

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

Can I propose to make this discussion cross-mailing list adding the hg mailing list to the CC? I think it would be a good discussion if we don't end up flaming. Let me know what you think about it

about the Windows+Git compatibility, you may consider TortoiseGit too for the not-CLI-oriented guys; I've seen it a while ago and it seems pettry well integrated with windows

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

If you tag a commit then you should be able to see how many commits there are from that one issuing a git describe (found on the internet) git commit -m'Commit One.' git tag -a -m'Tag One.' 1.2.3 git describe # => 1.2.3 git commit -m'Commit Two.' git describe # => 1.2.3-1-gaac161d git commit -m'Commit Three.' git describe # => 1.2.3-2-g462715d git tag -a -m'Tag Two.' 2.0.0 git describe # => 2.0.0

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).
Previous: Paolo BonziniNext: Dilip M
Message 37 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.