git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Witten <mfwitten@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
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 11:47:19 -0500	[thread overview]
Message-ID: <b4087cc50904260947n394d9c89nf0e821b0504091c5@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0904261208000.10279@pacific.mpi-cbg.de>

On Sun, Apr 26, 2009 at 05:13, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> 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).

Frankly, I think that it can be considered technical for Python
developers to choose an SCM written in Python. I can't fault them for
that.

  reply	other threads:[~2009-04-26 16:49 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
2009-04-26 16:47   ` Michael Witten [this message]
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=b4087cc50904260947n394d9c89nf0e821b0504091c5@mail.gmail.com \
    --to=mfwitten@gmail.com \
    --cc=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 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).