On Fri, 28 Dec 2012 06:16:59 -0800 (PST)
ericpar <e...@eparent.info> wrote:

>     But my colleagues wanted to have a GUI interface. I suggested
> them to try out TortoiseGit (I thought it was a natural replacement
> from TortoiseSVN) and they've been using it for about 6 months. We've
> been through all sorts of problems. My impression is that TortoiseGit
> is not fully adhering to Git's philosophy but some bugs might also be
> hidden in it.

I do not have much experience with TortoiseGit myself, but heard the
same opinion from a person I regard as a Git expert.  His major issue
with that tool was it trying to enforce a Subversion-inspired workflow
onto a developer.

>     We tried SmartGit for about 2 months now (I even gave it a try in
> order to be able to offer support to the team) and it's quite
> intuitive and works nicely. Free for personal use and cheap for
> professionnal (you pay a reasonable fee for a pack of licences).
>     So beware, if you're having problems, maybe your GUI client is to
> be blamed, not just a learning curve issue.

I would recommend looking at Git Extensions [1].  This is a F/OSS tool
which does work the way Git works, and has a nice UI (inspired by
TortoiseHg, I would say).  My only real issue with it last time I
checked was its inability to stage/unstage selected lines of a file
(rather than full patch hunks), but I consider this feature to be
rather advanced (`git gui` implements it, as does patch editing in
`git add --patch`).

1. http://code.google.com/p/gitextensions/


Reply via email to