I use SourceTree heavily for cherry-picking, mainly for Sinatra and Rack maintenance.

This involves me being on one release branch, for instance 1.3.x and going through commits on another branch, like master. However, I can only either few the history of the currently checked out branch or of all local branches (or of all branches). Just seing all the local branches in an overkill already, since I usually have multiple actively maintained branches (3 for Sinatra, 5 for Rack at the moment).

So it would be handy to be able to filter what branches should be displayed independently from the currently checked out branch.

It would also be handy to somehow make it easier to see a difference between merge commits and normal commits, esp. when scanning long, complex commit histories (say, either not list merge commits or use grey text instead of black or something similar).

I know this would probably be only useful to power users like me, but this is one of the few places where I really see an advantage of a UI like SourceTree over using the command line client.