My geekiness in one line.

[elfs]

git commit -m "Better, tighter. But still not enough relationship between Nefer and Sabrina to make this anything more than a 'lets get the sex out of the way, so we can see if we're compatible in more important ways' story. And I've written plenty of those."

Comments

[mikstera.livejournal.com]

I want to start using git for my own code. Are there any particular books / blogs / references / tools that you can recommend for how best to use git?

[elfs.livejournal.com]

I did a review (http://www.elfsternberg.com/2010/03/16/pro-git-apress-version-control-git-oreilly/) of two different GIT books, and found the non-O'Reilly one better for my purposes. That said, git takes some getting used to.

I strongly recommend using gitg or giggle to help you visualize your history and repository. I like giggle's history display better than gitg's, but I use gitg almost exclusively nowadays. Giggle is oriented toward teams, so "refresh" always takes you to the repository view, which is not what I want. I want to research what different branches I've got outstanding, and how they're integrated, and for that I need the history view.

Also, if you're using git in an SVN environment, as I am at work, I can't emphasize enough learning how "git svn rebase" and "git svn dcommit" actually work, and learn the "dry run" command.

[mikstera.livejournal.com]

Thanks!

I have a copy of Pragmatic Version Control Using Git. Since your review, have you happened to have a chance to peruse a copy?