Support cherry-picking merge revisions
By [email protected] on September 05, 2013 06:58 (imported from Google Code)
What steps will reproduce the problem?
Create a merge revision and try to cherry pick it on another branch.
What is the expected output? What do you see instead?
The cherry pick operation proceeds but the git subcall eventually fails since the --parent-number option is not supplied. I would appreciate a way to be able to cherry pick at least a single merge revisions.
What version of TortoiseGit and msysgit are you using? On
what operating system?
TortoiseGit 1.8.4 on Windows 7.
Please provide any additional information below.
I have no straightforward answer as to how to design the UI for that. But I think restricting this feature to single merge revisions would be helpful already. The reason is you often cherry-pick merges to backport the result of a feature/bugfix branch to another branch. Also, I do not know how the command line reacts if passed multiple merge and a --parent-number option.