I also think it is best choose base on Tortoise SVN. TortoriseGIt should be in windows platform only because it is extension of explore. Best regards Frank Li -----Original Message----- From: Nigel Magnay [mailto:nigel.magnay@gmail.com] Sent: Monday, November 03, 2008 6:00 PM To: Li Frank-B20596 Cc: Scott Chacon; Andreas Ericsson; Ian Hilt; git@vger.kernel.org Subject: Re: why not TortoiseGitQgit. 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Parag Warudkar | BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0] |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| David Miller | Re: [BUG] New Kernel Bugs |
