Ordinary committing cherry-pick: source S points to parent P, and result R points to target T. The dashed P-to-S patch transfer to R is not an ancestry link; S remains in its source history.

git cherry-pick re-applies a commit

Cherry-pick applies the change introduced by a selected commit to the current line of development. It is useful for a targeted backport when an older release needs one fix without the rest of a development branch. It does not move or delete the source commit, and it does not establish a merge relationship with the source branch. The target result must be reviewed as a change in its own environment. ...

November 25, 2027 · 5 min · XB Field Notes