Add a "cherry-pick" implementation

[Smolations]

Knowing about and remembering the usage of the git cherry-pick command is difficult. We should create a wrapper for this implementation which utilizes menus to drill down into branch commits to figure out what commit a user would or would not want to cherry-pick.

A nice-to-have feature with this wrapper would be the ability to run a diff while in the menu system which displays a git diff --name-status --porcelain or possibly opens a diff tool of some sort so users can verify that the changes they want are in the commit they are considering cherry-picking.

[chriscorwin]

Meh.

That's what SourceTree is for.

[Smolations]

Sourcetree can do just about everything GS can do, so why not just strip out everything in the scripts and just activate that app, especially since we can rely on every GS user having it installed.
{/sarcasm}

=]

P.S. Can we be diligent about deleting the original message text if responding to issues via email? Github doesn't seem to catch it and both you and McCulloh have submitted comments with all that extra text.