4 ms·
This is a great little guide. Nicely done! But my suggestion would be to use a nice Git GUI instead of the command line. SmartGit is free for non-commercial us
by Stratoscope 12y ago
This is a great little guide. Nicely done!
But my suggestion would be to use a nice Git GUI instead of the command line. SmartGit is free for non-commercial use and is quite wonderful. It's both easier to use than the command line (by a long shot) and it's actually more powerful too. Many operations that take multiple command line steps are a single command in SmartGit.
There is also SourceTree or the more limited Git GUIs for Mac and Windows from GitHub, but SmartGit is my favorite.
Maybe I'll take your writeup and convert it to a similar guide for SmartGit! :-)
- leeoniya 12y agodefinitely this. TortoiseGit, for instance, makes everything laughably easy for 95% of most workflows. For the other 5%, you can always drop down to commandline/terminal and then you really need to know what's going on.
- blktiger 12y agoGUI tools are nice in some situations, but I find they mostly slow me down. When I'm using Git I want to be fast and a hot-key command window plus the command line is about as fast as you can get.
- garyrob 12y agoMy philosophy is that when you use the command line, a) You learn the tool better, and b) wherever you are where there's git, you can use it. No need to install anything else. I had that philosophy back when I used Subversion, and I think it served me well. It really isn't that hard to use the command line. Especially if you use the subset in my post. I also suspect that GUI tools will generally have the power to deal with staging, branching, etc, and may thus be harder for a total newbie to understand, and more intimidating, than the few commands I outlined in the post. That's my take on it anyway. YMMV, of course!