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-aarch64-master-O3 in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-cpu2017rate/gnu-aarch64-master-O3.
discards 22810dd5c force: #134: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] discards 145570fdd force: #131: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] discards 5d3d30fd7 onsuccess: #128: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards c16d26692 onsuccess: #126: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 5aac75f51 onsuccess: #126: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new de864c49d onsuccess: #128: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 4fa0fa7d6 force: #131: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] new cf685766e force: #134: 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 (22810dd5c) \ 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: