documentation does not keep up with the new features constantly being added.integration with GitHub (Fork,clone, pull are all streamlined).easy to use installer that comes pre-packaged with all necessary and pre-requisite functionality to start out of the box (SSH Client, KDiff, msysgit).out of the box integration with Visual Studio (Windows Eclipse users only need msysgit, as they have their own GUI to replace the need for GitExtensions).built-in shell integration with Windows Explorer.ability to install as Administrator and all other users on the same PC can use it just like any regular user.visual gitk-like graphical display of codelines and branches, with all essential info available in tabs, eliminating any need to work with the unfriendly SHA's.The biggest advantages with using GitExtensions: I don't have much experience with TortoiseGit, but I installed, and am currently using GitExtensions v2.21. In my opinion both GUI tools are immature. Many files that they did not change show up as changed and the lock file prevents them from dealing with the problem, etc. After such an abort, non-coding users are always overwhelmed with problems. Another horror of Git Extensions is the frequent abort with "out of memory", when versioning many big files and pulling with rebase. The worst is a missing or incorrect password: Git Extensions just lets you wait forever, showing the same glowing bar as if it was doing something time-consuming. So with Git Extensions only, you sit in front of an enigmatic non-progress bar, not knowing what happens and whether something failed. Git Extensions has no option to show progress counters during a pull. Git bash is unavoidable to see the progress counters. Although even some of them additionally open up git bash. The Coders prefer git bash, the others use but hate git Extensions. But I did see lots of The crashes myself. The coders claim that Tortoise Git is not capable enough but I did not check that myself. My company tried both and quickly dropped Tortoise Git. You will avoid many headaches in the future. In the end, they dropped TortoiseGit and spend time learning git "the hard way" (shell, msysGit on Windows) and everyone has been happy since then.Ĭonclusion: Just use msysGit directly and properly learn git. As a personal experience, the company I work migrated from SVN to git after 2 years, and every single developer that used TortoiseGit ended up not really knowing what they are doing and sometimes screwing up their local repositories. and end up never really understanding how to work with git. The problem with TortoiseGit is that people who worked with TortoiseSVN will think everything will (or should) work exactly like in SVN. You will have a hard time understanding how to use git.Nearly the same UI as TortoiseSVN (if you already used TortoiseSVN, you know what to expect).Excellent integration with Windows (it's a shell extension).I don't know GitExtensions, but I can share my experience with TortoiseGit (alluded to by marc_s's comment):
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |