Re: why not TortoiseGit

From: Nigel Magnay <nigel.magnay@gmail.com>
Date: Nov 3, 2008, 10:00 UTC
Message-ID: <320075ff0811030200q606b76a8i16496cf7b8b1b7d2@mail.gmail.com>
In-Reply-To: <7FD1F85C96D70C4A89DA1DF7667EAE961E728C@zch01exm23.fsl.freescale.net>

Show 14 quoted lines

> I read some code of TortoiseSVN and TortoiseHg Code.
> At beginning, TortoiseGit can git command to get information like Qgit.
> After linkable library ready, replace "git command".
>
> I think TortoiseGit can start base on below way.
>
> 1.  Base on TortoiseHg, It is python Script.  Replace below hg operator
> with Git.
> 2.  Base on TortoiseSVN, It is developed with C++. Need VS2008.
> ToritoiseSVN provide some built in diff and merge tools.
> 3.  Base on Qgit, which provide some basic UI, such comment dialogbox,
> history view and file annotate.
>
>

TortoiseSVN is a good place to start because it separates out the windows icon decorators into a separate DLL (shared with TortoiseCVS). This is significant, as these are a finite resource in the windows shell, and so having a TortoiseSVN + TortoiseGIT on one machine and you might run out, and I'd imagine lots of people wanting both.

On the minus side, building (Tortoise)SVN requires a lot of environment setup just to get it to build - most of which can be immediately thrown away as it's specific to SVN.

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.