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

Re: [VOTE] git versus mercurial (for DragonflyBSD)

From
Jakub Narebski <jnareb@gmail.com>
Date
Oct 26, 2008, 18:55 UTC
Message-ID
<200810261955.10536.jnareb@gmail.com>
In-Reply-To
<ee2a733e0810260805n35c3a637v4739dda938a22518@mail.gmail.com>
I'm not sure if Mercurial mailing list is not subscribe only. Git isn't.
On Sun, 26 Oct 2008, Leo Razoumov wrote:
Show 19 quoted lines
> On 10/26/08, Maxim Vuets <maxim.vuets@gmail.com> wrote:
>> On 26 Oct 2008 15:15:57 +0100, Jakub Narebski <jnareb@gmail.com> wrote:
>>>
>>> 1. Documentation and ease of use.
>>>
>>>    Mercurial is supposedly better documented and easier to use; I
>>>    think this descends from the early days of Git, where it was not
>>>    very user friendly. IMHO Git has much improved since.  Mercurial
>>>    had 'hgbook' from the beginning; Git User's Manual is more recent.
>>
>> Also, there is http://book.git-scm.com/ that is similar to hgbook, I think.
>>
>>  Thanks for the comprarision!
> 
> I have been using Mercurial for about two years and am very
> comfortable with it.  Here are some cons and pros
> 
> Mercurial PROS:
> * Easier and more consistent UI. Newbie friendly.

I think that _might_ be example of "Worse is better" scenario, with Git having UI which evolved rather than was designed, and therefore less consistent.

Also if you are limiting to what is described in main chapters of 'hgbook', namely one branch (one "fork") per repository paradigm everything is simpler.

> * Better documentation. IMHO, hgbook is by far better than
>   http://book.git-scm.com/

And probably better than "Git User's Manual". There are lot of various git-related documentation: "Git Magic", "Git for Computer Scientists", "Git from bottoms up"...

> * Windows support (personally, I do not care)
And I think it is not important for DragonflyBSD.

Besides git _has_ MS Windows support, in the form of Cygwin and in the form of msysGit project. It is still not as full as Linux support (for example git-svn comes to mind), but it is not bad. Well, Mercurial has TortiouseHg, while Git-Cheetah is in very early stages...

Show 5 quoted lines
> 
> Mercurial CONS:
> * Less potential than git. Once Ted Tso even said that "git has more
>   legs than mercurial", see
>   http://thunk.org/tytso/blog/2007/03/24/git-and-hg/

I agree, and I think it is at least partially because of Git having cleaner design, even if you have to understand more terms at first.

> * Hg is strictly an SCM system while GIT is a content addressable file
>   system that can be used in other ways, hence the name Global
>   Information Tracker (GIT)

Errr... I think you are mislead by tongue-in-cheek backronym, which was created in the beginning, when git had very weak porcelain (i.e. SCM UI).

> * Recently, Hg development seems to have somewhat slowed down. To
>   simply put it, there is not enough room in the world for several
>   similar SCM systems. With git's pace and momentum the other SCMs
>   including Hg are fighting an uphill battle.

The competing _distributed_ version control systems left seems to be Bazaar-NG (Ubuntu), Mercurial (OpenSolaris, Mozilla), Git (Linux kernel, Freedesktop.org, Ruby on Rails people). There are many IDEs, many editors, many web browsers; there is Linux and there are *BSD; I hope that Mercurial would continue to be developed, and not vanish in obscurity like Arch and clones...

-- 
Jakub Narebski
Poland
Previous: Leo RazoumovNext: Arne Babenhauserheide
Message 5 of 65 in “[VOTE] git versus mercurial”
  1. waltOct 26, 2008
  2. Jakub NarebskiOct 26, 2008
  3. Maxim VuetsOct 26, 2008
  4. Leo RazoumovOct 26, 2008
  5. Jakub NarebskiOct 26, 2008
  6. Arne BabenhauserheideOct 27, 2008
  7. Leo RazoumovOct 27, 2008
  8. Arne BabenhauserheideOct 27, 2008
  9. dhruvaOct 27, 2008
  10. Arne BabenhauserheideOct 27, 2008
  11. Jakub NarebskiOct 27, 2008
  12. Arne BabenhauserheideOct 27, 2008
  13. Jakub NarebskiOct 27, 2008
  14. Leslie P. PolzerOct 27, 2008
  15. Arne BabenhauserheideOct 27, 2008
  16. Jakub NarebskiOct 27, 2008
  17. Benoit BoissinotOct 27, 2008
  18. Jakub NarebskiOct 27, 2008
  19. 0000 vkOct 27, 2008
  20. Jakub NarebskiOct 27, 2008
  21. Brandon CaseyOct 27, 2008
  22. Jakub NarebskiOct 27, 2008
  23. Nicolas PitreOct 28, 2008
  24. Felipe ContrerasOct 26, 2008
  25. Jakub NarebskiOct 26, 2008
  26. Felipe ContrerasOct 26, 2008
  27. waltOct 28, 2008
  28. Johannes SchindelinOct 28, 2008
  29. Git/Mercurial interoperability (and what about bzr?) (was: Re: [VOTE] git versus mercurial)Peter Krefting, Oct 28, 2008
  30. Johannes SchindelinOct 28, 2008
  31. Matthieu MoyOct 28, 2008
  32. Nicolas PitreOct 28, 2008
  33. Pieter de BieOct 28, 2008
  34. Miklos VajnaOct 28, 2008
  35. Miklos VajnaOct 28, 2008
  36. Theodore TsoOct 28, 2008
  37. Miklos VajnaOct 28, 2008
  38. Florian WeimerNov 1, 2008
  39. Santi BéjarNov 1, 2008
  40. Jakub NarebskiNov 1, 2008
  41. Florian WeimerNov 1, 2008
  42. Florian WeimerNov 1, 2008
  43. Jakub NarebskiNov 1, 2008
  44. Theodore TsoNov 1, 2008
  45. Linus TorvaldsNov 1, 2008
  46. Theodore TsoNov 2, 2008
  47. Peter KreftingNov 1, 2008
  48. Shawn O. PearceOct 29, 2008
  49. Boyd Lynn GerberOct 29, 2008
  50. Johannes SchindelinOct 29, 2008
  51. Boyd Lynn GerberOct 29, 2008
  52. Miles BaderOct 29, 2008
  53. David Soria ParraOct 27, 2008
  54. Jakub NarebskiOct 27, 2008
  55. Arne BabenhauserheideOct 27, 2008
  56. Miklos VajnaOct 27, 2008
  57. Arne BabenhauserheideOct 27, 2008
  58. Miklos VajnaOct 28, 2008
  59. Andreas EricssonOct 28, 2008
  60. Arne BabenhauserheideOct 28, 2008
  61. SZEDER GáborOct 28, 2008
  62. Marcin KasperskiNov 6, 2008
  63. Isaac JuradoNov 6, 2008
  64. Randal L. SchwartzOct 28, 2008
  65. Jakub NarebskiOct 27, 2008

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.