6 ms·
I use TortoiseGit (and was a long time user of TortoiseSVN before that), but I find it to be a poor substitute for the command line. I feel like they tried to m
by trun 14y ago
I use TortoiseGit (and was a long time user of TortoiseSVN before that), but I find it to be a poor substitute for the command line. I feel like they tried to make the names of git commands more user friendly, but having already grown accustomed to misnomers like "git checkout" it often takes me a little while to find the right action in TortoiseGit.
- slowpoke 14y agoThese aren't misnomers, they are intentional. Please read a bit into git before you accuse it of "misnaming" things.
- lancefisher 14y agoCheckout in SVN does not mean the same as it does in git. SVN Checkout is more like Git Clone. Checkout in git means change to a different branch. You "checkout a branch" in git. I think it is better for TortoiseGit to match the semantics of git rather than match the semantics of TortoiseSVN. It causes some confusion coming from SVN for sure, but once you start using git, you should learn its dialect. It would be worse if TortoiseGit did not match git's vocabulary.
- trun 14y agoThat was my point. For example, TortoiseGit presents "revert" instead of "checkout" (e.g. on a file, not a branch). "revert" in git actually means something else entirely.
- lancefisher 14y agoOh really? I used TortoiseSVN for a long time, and switched to the command line when I switched to git. I can see why TortoiseGit kept the "revert" naming, but I disagree about the choice.
- j-kidd 14y agoPerhaps the commands renaming was done to make TortoiseGit more consistent with TortoiseHg and TortoiseBzr?