Re: Git

On Sun, Feb 10, 2013 at 8:46 AM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> 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?
> * 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
> * 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.
>
> Please respond with your thoughs....

I was once active user (and even a small contributor) of TSVN.
Some years ago, I have started to use Git, and it was so powerful
that I almost totally moved away from SVN.

In my perception, TortoiseSVN is a last serious advantage that SVN
still has over Git.
I did try TortioseGit, and I agree that its interface is suboptimal.
Currently, I use either command line or standatd Git GUIs ("gitk" and
and "git gui").

So yes, for me and addition of Git to TortouseSVN might mean not only
a good tool, but perhaps on opportunity to return to TSVN development :)

However, I must note that this would be the single biggest change in the history
of TSVN, If you'll really decide to go this way, you should consider

1) Serious architectural changes. You know the saying "the programmer
should count like that: zero, one, many".
So, IMHO, correct way to include Git support is to include multiple
version control systems, including Hg and Bazaar.
I am, of course, not suggesting first-class support for all these at once,
but it is my experience that some design decisions are actually made
easier by avoiding temptation
to write "if (isGit)" kind of code.

2) A name change. TortoiseSVN is a great and well-known name, but
consider a phrase
"TortoiseSVN interface for Git is going to be better then
TortoiseGit", and I think you'll agree
that it is extremely confusing.
Some obvious candidates are "TortoiseVC", "TortoiseVersion" or just "Tortoise".

--
Alexander S. Klenin
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3048242
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].