This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-qc_speed-cpu2017rate/llvm-aarch64-master-O3 in repository toolchain/ci/base-artifacts/tcwg_bmk-qc_speed-cpu2017rate/llvm-aarch64-master-O3.

discards d328a65 force: #120: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] discards f902d20 force: #57: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-q [...] discards 483abe7 force: #56: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-q [...] discards d36985e force: #51: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-q [...] new edd2189 force: #51: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-q [...] new 2a6b1e9 force: #56: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-q [...] new 04fdda1 force: #57: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-q [...] new 03c529c force: #120: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...]

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (d328a65) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-qc_speed-cpu2017rate [...]

You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.

Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: