I've been using Git Tower for a couple of years now, and I'm happy to recommend v1.x as a solid GUI Git client for OS X. There are a few things I'd like to see improved, but the basics are quite good, and it's been relatively bug-free for me (although after doing a Twitter search, I can see some people had some problems with v1.x that I didn't).

Since Git Tower v2.0 was released, I've installed a trial and I've been using it on and off in parallel with Git Tower v1.x. In general, I like it. I think it's a fine evolution of Git Tower, I think the UI changes are mostly improvements, and I'm looking forward to using it full-time.

Having said that, I don't think it's ready for prime-time use, at least not for me. I've reported a few bugs already while using the trial, and I'm not the only one. And if you read over the mentions that @gittower has on Twitter, I think that's the general sentiment: looks good, but needs a bit more attention.

There has been a few point releases already (v2.0.3 at the time of this writing) and I expect there will be more. Basically, I'd say it looks like a promising upgrade, but if you're in no rush, it wouldn't hurt to wait a little longer. If you're curious, then download the trial in the meantime. If you really want to use Tower 2, you probably can, but accept there might be a few issues along the way.

One of my clients uses Subversion for source-control, and since I spend a lot of time in git anyway, I have been using git-svn to interact with their subversion repository. I like being able to commit locally even when I don't have a connection to their server, and then push the commits up to subversion when I do have a connection.

However, while git-svn lets me use some of the same tools that I use elsewhere, like Git Tower, the syntax for git-svn isn't exactly the same as either the git or svn clients, and it's not a perfect abstraction, which means that I occasionally have trouble remembering the exact syntax or the way to do something like find out which git commit corresponds to a subversion revision number.

Since I've been using Dash as a documentation browser as well, and since Dash 2.0 introduced cheat sheets, it seemed like I could save myself some time by writing a git-svn cheatsheet for Dash, which I did, and since it might save someone else some time, I contributed it to the Dash cheatsheet repo (using a pull request).

It's available now, so if you ever use git-svn and you use Dash, you should be able to download it within the app. And since the repository is open, you can even submit a pull request for changes to my cheatsheet if there are things you'd like to add to it (or, if you prefer, you can let me know, and perhaps I'll make the change).

One of my clients uses Subversion 1.7.x, and I've been connecting to it using Subversion 1.7 and git-svn installed via Homebrew. Last night, I upgraded to Mavericks, and this morning when I went to commit some changes, I discovered that all was not well.

This led me down a merry path involving:

• Discovering that subversion was broken because sqlite is now keg-only.
• Updating and upgrading homebrew.
• Reinstalling xcode command-line tools for Xcode 5.0.1.
• Checking out an older 1.7.10 recipe since my 1.7.9 installation was broken
• Modifying the subversion 1.7.10 recipe to work with 1.7.13 since 1.7.10 is no longer available on the Apache mirrors (change hash, sha)
• Telling Homebrew about Xcode 5.0.1 (modifying macos.rb)
• Reinstalling neon (--universal), serf (--universal), subversion (--java --universal)
• Fixing the Perl bindings for git-svn (using Victor Quinn's instructions, but replacing 5.12 for 5.16)