From: "Tim Visher" <tim.visher@gmail.com>
To: "Li Frank" <lznuaa@gmail.com>
Cc: sverre@rabbelier.nl, "Jakub Narebski" <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: Announce: TortoiseGit 0.1 preview version
Date: Sun, 14 Dec 2008 12:45:49 -0500 [thread overview]
Message-ID: <c115fd3c0812140945x79db8b85yb12c6b23c0479552@mail.gmail.com> (raw)
In-Reply-To: <1976ea660812140548k940a73buf307cd331b775f31@mail.gmail.com>
On Sun, Dec 14, 2008 at 8:48 AM, Li Frank <lznuaa@gmail.com> wrote:
> I think TortoiseGit can make git popular at windows enviroment.
> Window user is waiting for the good UI. Porting from TortoiseSVN is
> fastest way.
I think you nailed it on the head there, Li. I had a hell of a time
trying to convince my team to use Subversion over (*gasp*) VSS,
despite the abominable network performance that we were getting with
VSS _and_ all of its obvious flaws (which they freely admitted), until
I finally showed them Tortoise (which I don't personally use) and then
they were all for it. Something like Tortoise for Git on Windows
would remove a __huge__ barrier to entry for most people that aren't
already comfortable with the command line. As simple as git is from
the command line, certain people just don't want to bother.
--
In Christ,
Timmy V.
http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail
next prev parent reply other threads:[~2008-12-14 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 8:33 Announce: TortoiseGit 0.1 preview version 李智
2008-12-13 14:21 ` Tim Visher
2008-12-14 12:27 ` Li Frank
2008-12-14 13:09 ` Jakub Narebski
2008-12-14 13:28 ` Sverre Rabbelier
2008-12-14 13:48 ` Li Frank
2008-12-14 17:45 ` Tim Visher [this message]
2008-12-14 13:29 ` Li Frank
2008-12-15 13:56 ` Jakub Narebski
2008-12-15 14:19 ` Li Frank
[not found] ` <1976ea660901060645r641d73e6ob4e03747f1860b6a@mail.gmail.com>
2009-01-06 23:05 ` Jakub Narebski
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=c115fd3c0812140945x79db8b85yb12c6b23c0479552@mail.gmail.com \
--to=tim.visher@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=lznuaa@gmail.com \
--cc=sverre@rabbelier.nl \
/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).