Does TortoiseGit actually make Git a lot easier to use like TortoiseSVN? [closed]

by

I think, you lose a lot of functionality of Git when you use TortoiseGit. From my point of view, TortoiseGit gives the user the feeling of using SVN while the actual back-end is Git.

When I was working with SVN repos, the only client I used was TortoiseSVN. No console at all.

But learning Git was quite console-driven for me, so I use the console to work with Git. There are some use cases when I fire up my TortoiseGit, for example when reading logs or resolving conflicts. But instead of Tortoise, I could also use gitk for that. And — not to forget — TortoiseGit is not the most stable piece of software.

In my opinion, the only right to exist for TortoiseGit is to catch the TortoiseSVN users that are switching to Git: they can stick to their used explorer integration and don’t have to learn a new tool when using a new VCS (IMHO, the learning curve of Git is steep enough, so some people might first focus on learning the basics of git before discovering the power of the console). And the point-and-click Windows guys don’t have to communicate with their system through a console. That’s it.

I share the opinion of Noufal: if you want to use Git, take the console, if you want to play with it, take TortoiseGit.

Edit:
I do respect the work of the TortoiseGit project team that eases transition from SVN to Git for users that used TortoiseSVN before. But in my opinion: to use the full power of Git, you have to start up your Git bash. You can work with Git using TortoiseGit only, but then, you’re just scratching the surface of Git.

By the way: the TortoiseGit project description says:

TortoiseGit supports you by regular tasks, such as committing, showing logs, diffing two versions, creating branches and tags, creating patches and so on […].

So their own view of their project shares mine: TortoiseGit for scratching the surface but you’ll need other tools (i.e. the console) to discover the whole beauty of Git.

More Related Contents:

  1. How to resolve “git did not exit cleanly (exit code 128)” error on TortoiseGit? [closed]
  2. TortoiseGit save user authentication / credentials
  3. Remove saved credentials from TortoiseGit
  4. Invalid SSL certificate when pushing to Git server
  5. Can I update a forked project, on git, to the original/master copy?
  6. How to install/setup TortoiseGit to work with GitHub
  7. Support for password authentication was removed on August 13, 2021
  8. Does TortoiseGit work with PortableGit-x.x.x.x-previewyyyyyy? What are compatible git versions for TortoiseGit?
  9. New to GitHub, how to run the commands on Windows?
  10. How to find the nearest parent of a Git branch
  11. How do I push amended commit to the remote Git repository?
  12. Re-doing a reverted merge in Git
  13. How to find/identify large commits in git history?
  14. How to squash all git commits into one?
  15. How to find a deleted file in the project commit history?
  16. Cleaning up old remote git branches
  17. Remove specific commit
  18. Git: Could not resolve host github.com error while cloning remote repository in git
  19. Git: ignore some files during a merge (keep some files restricted to one branch)
  20. Why does Git tell me “Not currently on any branch” after I run “git checkout origin/”?
  21. Can deleted .git be restored?
  22. git – merge conflict when local is deleted but file exists in remote
  23. How to get a list of all files that changed between two Git commits?
  24. What is the difference between git push origin and git push origin master
  25. When I do “git push”, what do the statistics mean? (Total, delta, etc.)
  26. Checkout old commit and make it a new commit [duplicate]
  27. Adding git branch on the Bash command prompt
  28. Remote rejected (shallow update not allowed) after changing Git remote URL
  29. Unable to authenticate with Git Bash to Visual Studio Team Services
  30. git clone hangs forever on github

Leave a Comment