Quote:
Originally Posted by bvesco
Unfortunately there doesn't seem to be a clean way to do complex merging while keeping a nice revision graph. For instance, if you cherry pick a revision from another branch and later merge that other branch you now have two different unconnected nodes on your revision graph that both point to the same commit. Confusing and cluttered.
|
I think this is the result of the cherry picking which as far as I understand produces a commit unrelated to the original commit. This thread seems interesting:
http://stackoverflow.com/questions/1...merge-workflow
reading this an other stuff makes me think cherry picking should be used very carefully.