We need a `git-webkit trace` command that, when given a hash/identifier/revision, will find the original commit of a cherry pick. This is effectively a linked list, because the commit cherry picked might also itself be cherry-picked.
<rdar://problem/97455957>
As I put this together, it turned out that this same idiom works for reverts and follow-up fixes, as long as we keep track of relationship type.
Pull request: https://github.com/WebKit/WebKit/pull/4072
Committed 254997@main (d3e19e632f18): <https://commits.webkit.org/254997@main> Reviewed commits have been landed. Closing PR #4072 and removing active labels.
Committed 252432.496@safari-7614-branch (57f0dd3bd58e): <https://commits.webkit.org/252432.496@safari-7614-branch> Reviewed commits have been landed. Closing PR #90 and removing active labels.