After a hectic Christmas of stuffing my face with Turkey, Cake and Chocolate, I have had to power on my brain again and get back to work. Before Christmas, high on the sugary goodness of Git branches, I disconnected all my SVN repositories and got Git set up instead… maybe not such a good idea after all.
Git is a powerful platform, most likely more so than SVN, but it’s just not as easy to use. All the knowledge I pulled up from the tutorials mentioned in my last post has faded and I am struggling with even simple tasks. I’ve taken it upon myself to go over them again and I am starting to feel a little strained at all the extra steps I now have to take when opposed to SVN.
SVN:
- Right click, click Commit.
- Enter message in provided box.
- Check files in nicely formatted table form.
- Click Commit again.
Git:
- Right click, click Open Git Bash.
- Type:
- “git add .” ensuring that the junk I don’t want is ignored.
- “git commit -m ‘Some Message’” without support for easy formatting the message.
- “git checkout master” to return to the master branch (good practice).
- “git merge dev” or whatever the branch was before (good practice).
- “git push origin master” to commit it to a central repos.
It’s not Git’s fault that it’s like this, SVN was once the same and only with time did the excellent tool support come about. I do think Git is the future as they keep plugging the gaps where it doesn’t measure up to SVN but it’s whether now is the time to use it? I’m not averse to typing, it’s just it takes a lot longer and isn’t as user friendly as a big box that I can just click on.
I have one more thing I’d like to try before I commit to either one for the time being and I will follow it up in a post shortly.
Nat Ryall
January 8, 2010 at 4:40 pm
This is a great accompanying post: http://stackoverflow.com/questions/161541/svn-vs-git