Re: [egit-dev] Cherry pick workflow?

[Chris Aniszczyk <caniszczyk@xxxxxxxxx>]

On Wed, Nov 10, 2010 at 12:03 PM, Shawn Pearce <spearce@xxxxxxxxxxx> wrote:
> The problem with cherry-pick is you need to designate the commit that
> you want picked.  Putting the action in the history view makes it easy
> to designate a commit node to cherry-pick.

Yes, but it forces you to go to the history view which I don't like for my case.

I have a change I want to cherry pick from github...
   - git remote add -f <username> git://github.com/<username>/repo.git
   - git fetch <username>
   - git cherry-pick <sha1>

I don't see how you could use the history view for this. For me it
would be more natural to add the remote, fetch the objects and then
open a 'Open Type' similar dialog to hunt for commits to cherry pick.

-- 
Cheers,

Chris Aniszczyk
http://aniszczyk.org
+1 860 839 2465