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-spec2k6/llvm-aarch64-master-O2 in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/llvm-aarch64-master-O2.

discards cfb09290 onsuccess: #139: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 8651f99d onsuccess: #138: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards c43f2aa9 onsuccess: #136: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 0220a133 onsuccess: #135: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new c9c78cd3 onsuccess: #135: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new dd6b3d4b onsuccess: #136: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 73c9ac74 onsuccess: #138: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new a755c92b onsuccess: #139: 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 (cfb09290) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-spec2k6/l [...]

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: