PS3 was a non-trivial rebase, and copyMaxScore is not enabled on the Code-Review label in either All-Projects or chromiumos.

I'm moving this over to the chrome-infra side with three suggestions to consider:

1. Modify Commit-Bot to revote on behalf of existing reviewers after landing the change. It already has logic in place to delete Commit-Queue votes on behalf of other users.

2. Set copyMaxScore = true to the Code-Review label section in a relevant project config. This means that unless explicitly revoked, approvals would pass on to subsequent patch sets no matter what is uploaded.

3. Get Gerrit to offer a more nuanced setting to carry votes forward in situations like this.

Moved issue gerrit:6269 to now be  issue chromium:725109 .

This is a chromeos infra question; Chrome and related projects already carry the Code-Review label forward across new patchsets because that's how Rietveld behaved. ChromeOS does not carry the label forward for historical reasons. If they want to change that, they're welcome to, but it's not a policy decision for non-ChromeOS folks to make, I don't think.

Commit message changes can change actual behavior within build system, since CQ-DEPEND messages are parsed from them. Therefore, out of caution, updates to commit message are considered to require the same level of approval (committer access) to run through the the pre-cq/cq/etc.