2 ms·
The Gerrit review system tags every change (i.e. commit) with a durable Change-ID, which is represented int the log message, usually as the last line, like this
by kazinator 5y ago
The Gerrit review system tags every change (i.e. commit) with a durable Change-ID, which is represented int the log message, usually as the last line, like this:
Change-Id: I7321a7fddab667af7a418eeeb7d48c0240570260
The Change-Id will be the same whenever that commit is cherry-picked anywhere, even if it has to change due to merging. It is not a hash, but a random UUID.
If you trowel through the log messages you can find the places where that change has "been" by looking for the Id.
- wildfire 5y agoA common problem when using Gerrit is the Change-Id being copied across from different branches (via, for example, git cherry-pick). The idea is ... interesting, but the implementation of Change-Id has quite a few problematic corner-cases which make normal git operations (rebase, cherry-pick, merge) more delicate than the need to be.