From: "Nigel Magnay" <nigel.magnay@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Li Frank" <Frank.Li@freescale.com>,
"Scott Chacon" <schacon@gmail.com>,
"Andreas Ericsson" <ae@op5.se>, "Ian Hilt" <ian.hilt@gmx.com>,
git@vger.kernel.org
Subject: Re: why not TortoiseGit
Date: Mon, 3 Nov 2008 13:39:47 +0000 [thread overview]
Message-ID: <320075ff0811030539q476ab4f4kd332a37acdc1ca87@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0811031425080.22125@pacific.mpi-cbg.de.mpi-cbg.de>
>> But it doesn't look like a hard project to me, just requires stripping
>> out a lot of junk and re-patching callouts to a git executable (which
>> could be the standard git tools) and a minimal git library that knows if
>> files are dirty.
>
> I only wish that people would put their code where there mouth is.
>
> At least with GitCheetah, we have working code, _and_ an opportunity to go
> cross-platform.
>
Well, hey, I don't care there's no TortoiseGit. I looked at these
things back when I had colleagues stuck on Windows, and at the time
wanted to try and wean them off SVN.
The shell-icon overlay limit on Windows looked a significant problem
to me, and a good reason for at least re-using that bit of code (which
is common to even tortoiseCVS). It looked like it had been through a
significant number of iterations to get platform shell subtleties
right.
I even looked at wacky things, like using IKVM.Net and JGit to hack it
quickly, but that's a non-starter because of MS' stupid
one-clr-per-process.
That's what I found. Maybe it'll be useful for anyone else that wants
to continue. Since it's not an itch for me any more, and it won't feed
my children, until someone that cares enough does something there
won't be one.
next prev parent reply other threads:[~2008-11-03 13:41 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
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 [this message]
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=320075ff0811030539q476ab4f4kd332a37acdc1ca87@mail.gmail.com \
--to=nigel.magnay@gmail.com \
--cc=Frank.Li@freescale.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=ian.hilt@gmx.com \
--cc=schacon@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).