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

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

discards 11a8ae4 onsuccess: #109: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards c1d311d onsuccess: #108: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 4af3e59 onsuccess: #107: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 1545d20 force: #106: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] new bfdd283 force: #106: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] new 479826f onsuccess: #107: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new c35cb8c onsuccess: #108: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 1c19be8 onsuccess: #109: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...]

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 (11a8ae4) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-cpu2017ra [...]

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: