Before fork TortoiseGit from TortoiseSVN at 5 years ago, I ask you about if you are interested in implement Git support. You said you have not time to do that.
I have to fork TortoiseSVN to support git at that time. Git become more and more popular during this 5 year, it is very normal to want to support in tortoisesvn. Many developer, you and me is part time to contribute code and test production, we shouldn't waste their efforts to do duplicated work.
TortoiseGit and TortoiseSVN already exist 5 years in worlds. It will be much confused if TortoiseSVN also support Git. If you want to create total new project to include all SCM, I support it. But I suggest this new project should cross linux, MAC and windows. Many user use MAC and linux than 5 years ago.
> Not sure how to start, but I'd like to discuss an idea:
> I've been trying out Git on and off ever since it became available. At
> first it wasn't even a serious option on Windows, but of course it
> improved. Implementing Git in TSVN was always an option for me, but the
> official API was (and still is) completely unusable. Only the
> non-official libgit2 library seemed like a real option, even though for
Libgit2 is far from stable and usable. TortoiseGit use stable part of libgit2, like get hash value, get head tree information.
You implement clone with libgit2, but there are many issues, like you can't clone from code.google.com, can't support ssh.
> a long time it lacked the most basic features so it wasn't an option either.
> But now as you might have heard, Microsoft is using libgit2 as well for
> Visual Studio - and when I checked out libgit2 again it's now actually
> usable. And frigging small! It's only about 600kbytes big and can do
> almost everything that's necessary - compare that to the megs required
> for basic SVN and you can see the size difference really is astonishing :)
> For tests, I've implemented the clone command with libgit2 in TSVN and
> it works quite well.
libgit2 can't support clone from code.google.com.
> But before I go any further, I think we need to first discuss a few
> things here:
> * should we even add Git support to TSVN?
> Or should we concentrate on SVN alone?
I suggest you concentrate SVN. But we can consider how to create common library to share two project code.
Some application(like tortoiseplink, tortoisemerge and so on) is reused by tortoisegit.
> * there's already TortoiseGit, so what about that?
> Note: while I've installed TGit on my machine, I never really liked
> it's UI - it's IMHO too complicated
You can provide your suggestion. We can improve it.
Complex UI is caused by git powerful. In earlier version of tortoisegit, UI is almost the same as tortoiseSVN.
> * if you look at the TGit source you'll see that a *lot* of its code
> was taken from TSVN - so if we add Git support ourselves it won't
> add a lot to the size of TSVN.
> If we add Git support: make no mistake, this will take a long time to
> get it to a usable state. While I got the clone command working withing
> a few hours and most commands will take not much more time, there are a
> lot of commands to implement and even more UI implementations and
> decisions to make.
You will meet many problems when implement other command.
> Please respond with your thoughs....
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest interface to (Sub)version control
> /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-03-04 05:06:50 CET