如果我永远不合并它们，那么在两个分支A和B之间的git中采摘樱桃的危险是什么? [英] What are the perils of cherry picking in git between two branches A and B if I am never going to merge between them?

问题描述

我已经阅读了雷蒙德·陈(Raymond Chen)的精彩文章，标题为停止挑选樱桃，开始合并

I have read the excellent series of posts by Raymond Chen titled Stop cherry-picking, start merging

我完全理解，如果我们以后要合并分支机构，摘樱桃是邪恶的.

And I totally understand that cherry-picking is evil if we are going to merge the branches afterwards.

但是，假设我从未合并两个分支.在这种情况下，有没有采摘樱桃的危险?

But suppose I never merge the two branches. Are there any perils of cherry-picking in this case?

推荐答案

不完全是没有"，但风险很低.

Not exactly "none", but low risk.

唯一的问题仍然是根据不是精心挑选的另一个更改来进行更改:在源分支上进行合并时，结果合并将无法在目标分支中进行.
称为"忽略功能依赖项".

The only issue remains to pick up a change depending on another change that is not cherry-picked: the resulting merge would not work in the destination branch while it was working on the source branch.
That is called "ignoring functional dependencies".

这篇关于如果我永远不合并它们，那么在两个分支A和B之间的git中采摘樱桃的危险是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！