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

Re: Google Code: Support for Mercurial and Analysis of Git and Mercurial

From
Jakub Narebski <jnareb@gmail.com>
Date
Apr 26, 2009, 08:16 UTC
Message-ID
<m363grq13i.fsf@localhost.localdomain>
In-Reply-To
<200904260703.31243.chriscool@tuxfamily.org>
Christian Couder <chriscool@tuxfamily.org> writes:
Show 11 quoted lines
> For information, now Google Code supports Mercurial for project hosting:
> 
> http://google-code-updates.blogspot.com/2009/04/mercurial-support-for-project-hosting.html
> 
> Mercurial was choosen over Git because of this (one year old) analysis:
> 
> http://code.google.com/p/support/wiki/DVCSAnalysis
> 
> There is this article on LWN about the analysis:
> 
> http://lwn.net/Articles/330138/

It is a pity that the choice was based on year old analysis. One year for actively developed and fast moving targets such like Git and Mercurial is ages in terms of development history. But I guess this is unavoidable.

For example periodic "maintenance" (garbage collecting) is nowadays quite automatic in git, with fetching into pack, periodic repacking if number of loose objects is above tthreshold, and "git gc --auto".

Whether Mercurial or Git has better UI and better documentation is IMHO a matter of debate. Git documentation is much better that it was, with "Git User's Manual" and "Git Community Book"; UI also is being improved.

I can't comment on MS Windows support, but AFAIK Mercurial has better support here than Git.

The deciding feature (well, one of deciding features) was the fact that Mercurial has better HTTP support... I guess (it was not obvious from the analysis, but it was hinted at) that Mercurial uses its custom protocol over HTTP, as opposed to "dumb" HTTP protocol support in Git.

Perhaps it is time to restart work on _"smart" HTTP protocol_?
-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Michael WittenNext: Paolo Ciarrocchi
Message 3 of 26 in “Google Code: Support for Mercurial and Analysis of Git and Mercurial”
  1. Christian CouderApr 26, 2009
  2. Michael WittenApr 26, 2009
  3. Jakub NarebskiApr 26, 2009
  4. Paolo CiarrocchiApr 26, 2009
  5. Johannes SchindelinApr 26, 2009
  6. Jakub NarebskiApr 26, 2009
  7. Johannes SchindelinApr 26, 2009
  8. Alex BlewittApr 26, 2009
  9. Shawn O. PearceApr 27, 2009
  10. Paolo CiarrocchiApr 26, 2009
  11. Matthias AndreeApr 26, 2009
  12. Jakub NarebskiApr 26, 2009
  13. Matthias AndreeApr 26, 2009
  14. Jakub NarebskiApr 26, 2009
  15. A Large Angry SCMApr 26, 2009
  16. Michael WittenApr 26, 2009
  17. Johannes SchindelinApr 26, 2009
  18. A Large Angry SCMApr 26, 2009
  19. Johannes SchindelinApr 26, 2009
  20. A Large Angry SCMApr 26, 2009
  21. James CloosApr 26, 2009
  22. Johannes SchindelinApr 26, 2009
  23. Michael WittenApr 26, 2009
  24. Miles BaderApr 26, 2009
  25. Shawn O. PearceApr 27, 2009
  26. Mark LodatoApr 30, 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.