Discussion:
Git Extensions vs other tools
Ryan Langton
2013-04-10 20:05:26 UTC
Permalink
History:
* Used TortoiseSVN for years - it was ok but seemed to have a tough time
with conflicts, probably more of an issue with SVN than tortoise.
* Used GitBash for a year - never really got used to command line and
thought it took too long to do anything, not a fan.
* Used SmartGit for a year - loved it, does everything I need, nice GUI.

Now my license has run out and I'm being asked to use the cheaper (aka
free) alternative, GitExtensions. What's the ramp up time for learning the
tool? What's the disadvantages it has? Any other tips?

Thanks,
Ryan
--
You received this message because you are subscribed to the Google Groups "GitExtensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gitextensions+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Chris Harris
2013-04-11 05:59:06 UTC
Permalink
I haven't tried SmartGit, but I've found Git Extensions to be a very
usable and helpful interface to Git. A year or two ago I convinced my
team to switch from SVN to Git, and since my team was accustomed to
GUI tools like TortoiseSVN, Git Extensions was instrumental in making
this work. Though it's also nice to be able to fall back to the git
command-line if needed.

If you are already familiar with Git I think the transition should be
quite quick, as the GUI maps pretty obviously onto command-line
equivalents. If not, I don't think the tool is especially hard to get
the hang of, but I would recommend making sure at least one person on
the team understands git at an intermediate level or beyond, and can
help explain what distributed source control is all about and answer
questions that emerge about branching, merging, rebasing,
cherry-picking, etc..

One of the main stumbling blocks for people on my team was during
pulls whether to use the rebase radio button or the normal merge radio
button. In our case, the correct answer is almost always to rebase.

So far in my experience the biggest disadvantages have been regarding
filtering and searching through the commit history; this seems a bit
quirky, and slower than I would expect. I haven't yet figured out how
much of this is inherent to git vs how much has to do with Git
Extensions in particular.
Post by Ryan Langton
* Used TortoiseSVN for years - it was ok but seemed to have a tough time
with conflicts, probably more of an issue with SVN than tortoise.
* Used GitBash for a year - never really got used to command line and
thought it took too long to do anything, not a fan.
* Used SmartGit for a year - loved it, does everything I need, nice GUI.
Now my license has run out and I'm being asked to use the cheaper (aka free)
alternative, GitExtensions. What's the ramp up time for learning the tool?
What's the disadvantages it has? Any other tips?
Thanks,
Ryan
--
You received this message because you are subscribed to the Google Groups
"GitExtensions" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "GitExtensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gitextensions+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Loading...