Merge commit always need a redo when using cherry-pick strategy

[Lloyd Su]

Hi All,

We are using cherry-pick strategy in gerrit, when we push multiple patches including some merge commits.

I found every time, when a change got submitted (cherry-picked), following merge commits must be rebased (re-merged) manually and upload again.

Is that possible that gerrit can support a server side re-merge based on the new parent commit that generated by cherry-pick?  If new parents and old parents contains same tree sha1? I think all the necessary information already in the gerrit db to do that?

[Lloyd Su]

Please ignore this one, thanks

Sorry I posted a duplicate, because I cannot found this one -_-! 

Anybody know the answer please reply to the new thread.

https://groups.google.com/forum/#!topic/repo-discuss/54-TS7tzs3c