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-arm-master-O2 in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/llvm-arm-master-O2.
discards ab2af33c force: #74: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-c [...] discards 2dd33319 onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards db425613 onsuccess: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 944af5ca onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 432ec57a onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new fc6c2cf8 onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new aea6c7de onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 11709651 onsuccess: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 9b6fc927 onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 947c115e force: #74: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-c [...]
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 (ab2af33c) \ 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 5 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: