From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org
Subject: Re: Google Code: Support for Mercurial and Analysis of Git and Mercurial
Date: Sun, 26 Apr 2009 12:13:23 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.1.00.0904261208000.10279@pacific.mpi-cbg.de> (raw)
In-Reply-To: <200904260703.31243.chriscool@tuxfamily.org>
Hi,
On Sun, 26 Apr 2009, Christian Couder wrote:
> 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/
FWIW some little bird (yes, related to the Google Code team) told me that
the real reason was because a certain person important in Git development
was upsetting the Google Code team. It _might_ be related to the fact
that the original Googe Code team had a substantial involvement in
Subversion...
So, don't believe that the reason Git is not supported by Google Code is a
technical one (just like it was no technical reason at all for Python to
choose Hg over Git).
Oh, and I have to be very clear on some important point: they are free to
choose what they want. I, for one, am happy that not everybody and her
dog uses Git. That way, we can steal cute ideas from other projects like
Hg or Bazaar.
Ciao,
Dscho
next prev parent reply other threads:[~2009-04-26 10:14 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
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 [this message]
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=alpine.DEB.1.00.0904261208000.10279@pacific.mpi-cbg.de \
--to=johannes.schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.