"Remo Senekowitsch" <remo@xxxxxxxxxxx> writes: > Doesn't a patch set ID suffer from the same kind of ambiguity the > change-id supposedly does? Patch sets can be split and merged, a commit > from one patch set can be cherry-picked into another. What patch set ID Correct. I still prefer it over the change IDs between these two incomplete mechanisms. To resolve the ambiguity, you'd probably go all the way to an approach like "in addition to the usual parent-child relationship, we record the change evolution relationship so that there is a record on each commit what 'predecessor commit(s)' it was derived from".
