> Since it's not via change-set ids, then does it keep track of related commits in a branch? It is via changeset-Ids correlating to individual commits. The ch

> Since it's not via change-set ids, then does it keep track of related commits in a branch? It is via changeset-Ids correlating to individual commits. The changeset-Ids only serve as a permanent identifier to individual commits. Everything else comes via the regular backward chain of commit IDs. (Until it hits an already-known/merged commit or an unrelated commit which it knows a changeset-ID for. Not sure of the exact details, but it works as one would expect.) (Even though Gerrit does support branches and submitting commit to specific branches, etc. we use it in a branchless way in almost all of our projects. Nor do we do merge commits.)