From: Jakub Narebski <jnareb@gmail.com>
To: "Li Frank-B20596" <Frank.Li@freescale.com>
Cc: <git@vger.kernel.org>
Subject: Re: why not TortoiseGit
Date: Thu, 30 Oct 2008 18:59:06 -0700 (PDT) [thread overview]
Message-ID: <m3bpx1h6e6.fsf@localhost.localdomain> (raw)
In-Reply-To: <7FD1F85C96D70C4A89DA1DF7667EAE96125890@zch01exm23.fsl.freescale.net>
"Li Frank-B20596" <Frank.Li@freescale.com> writes:
> There are TortoiseCVS, TortoiseSVN, TortoiseBzr, TortoiseHg
> Why not ToroiseGit?
Because GitCheetah
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-10-31 2:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 1:44 why not TortoiseGit Li Frank-B20596
2008-10-31 1:59 ` Jakub Narebski [this message]
2008-10-31 2:02 ` Li Frank-B20596
2008-10-31 3:07 ` George Shammas
2008-10-31 3:53 ` Miles Bader
2008-10-31 12:19 ` Ian Hilt
2008-10-31 12:35 ` Andreas Ericsson
2008-10-31 15:57 ` Scott Chacon
2008-11-02 14:14 ` Li Frank
2008-11-03 10:00 ` Nigel Magnay
2008-11-03 13:26 ` Johannes Schindelin
2008-11-03 13:39 ` Nigel Magnay
2008-11-04 6:36 ` Li Frank
2008-11-04 12:52 ` Johannes Schindelin
2008-11-11 1:51 ` Li Frank
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=m3bpx1h6e6.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=Frank.Li@freescale.com \
--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).