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/gnu-arm-master-O2 in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-cpu2017rate/gnu-arm-master-O2.

discards bd9f501b3 onsuccess: #82: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards e70f5b37b onsuccess: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards c4350d9a9 onsuccess: #80: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 741507fff onsuccess: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 603ef9611 onsuccess: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 2451e9336 onsuccess: #80: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 776f8c23b onsuccess: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 0e71e2558 onsuccess: #82: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]

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 (bd9f501b3) \ 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: