Today I faced with one problem. My teammate created branch from master. He developed one feature in this branch and after that developed two subfeatures in subfeature\'s branche
Note that you need a git1.7.6+ for git rebase --preserve-merges
to work properly.
rebase --preserve-merges --onto
didn't work before ("git rebase --preserve-merges --onto doesn't preserve merges")rebase --preserve-merges
had issue in some instance:
Long story short: You just completed a merge and somebody has pushed a commit before you were able to push yours. The solution is to make git aware of the merge you did.
git rebase --preserve-merges <upstream>
or
git rebase -p <upstream>
But there's a problem, if your merge had conflicts that you solved they won't be picked up by the rebase machinery.
And you will end up resolving the conflicts again ... at least this is the case with git version 1.7.5.4
(That would call for git rerere)
Did you cherrypick every commit one by one by hand?
Just run git rebase -i master feature
and rewrite the history as you please.