From: A Large Angry SCM <gitzilla@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Christian Couder <chriscool@tuxfamily.org>, git@vger.kernel.org
Subject: Re: Google Code: Support for Mercurial and Analysis of Git and Mercurial
Date: Sun, 26 Apr 2009 10:54:48 -0400 [thread overview]
Message-ID: <49F475B8.20903@gmail.com> (raw)
In-Reply-To: <m363grq13i.fsf@localhost.localdomain>
Jakub Narebski wrote:
> Christian Couder <chriscool@tuxfamily.org> writes:
>
>> 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_?
>
Another important criteria was which, both or neither of Git and Hg
would actually work and perform well on top of Google Code's underling
storage system and except to mention they would be using Bigtable, the
report did not discuss this. Git on top of Bigtable will not perform well.
Read the paper and do the math if you are interested.
http://labs.google.com/papers/bigtable-osdi06.pdf
next prev parent reply other threads:[~2009-04-26 14:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 5:03 Google Code: Support for Mercurial and Analysis of Git and Mercurial Christian Couder
2009-04-26 7:12 ` Michael Witten
2009-04-26 8:16 ` Jakub Narebski
2009-04-26 8:23 ` Paolo Ciarrocchi
2009-04-26 10:07 ` Johannes Schindelin
2009-04-26 10:16 ` Jakub Narebski
2009-04-26 10:18 ` Johannes Schindelin
2009-04-26 12:02 ` Alex Blewitt
2009-04-27 20:31 ` Shawn O. Pearce
2009-04-26 10:21 ` Paolo Ciarrocchi
2009-04-26 9:21 ` Matthias Andree
2009-04-26 10:09 ` Jakub Narebski
2009-04-26 11:47 ` Matthias Andree
2009-04-26 19:57 ` Jakub Narebski
2009-04-26 14:54 ` A Large Angry SCM [this message]
2009-04-26 16:45 ` Michael Witten
2009-04-26 16:56 ` Johannes Schindelin
2009-04-26 17:33 ` A Large Angry SCM
2009-04-26 17:45 ` Johannes Schindelin
2009-04-26 18:00 ` A Large Angry SCM
2009-04-26 18:59 ` James Cloos
2009-04-26 10:13 ` Johannes Schindelin
2009-04-26 16:47 ` Michael Witten
2009-04-26 22:24 ` Miles Bader
2009-04-27 21:15 ` Shawn O. Pearce
2009-04-30 0:00 ` Mark Lodato
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49F475B8.20903@gmail.com \
--to=gitzilla@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).