Bug 244859
| Summary: | [git-webkit] Add trace command | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Jonathan Bedard <jbedard> |
| Component: | Tools / Tests | Assignee: | Jonathan Bedard <jbedard> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Jonathan Bedard
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jonathan Bedard
<rdar://problem/97455957>
Jonathan Bedard
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.
Jonathan Bedard
Pull request: https://github.com/WebKit/WebKit/pull/4072
EWS
Committed 254997@main (d3e19e632f18): <https://commits.webkit.org/254997@main>
Reviewed commits have been landed. Closing PR #4072 and removing active labels.
EWS
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.