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_vect-spec2k6/llvm-arm-master-O3 in repository toolchain/ci/base-artifacts/tcwg_bmk-code_vect-spec2k6/llvm-arm-master-O3.
discards 474813ee onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 36b54b5b force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-c [...] discards 9ee8b230 onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 7a9549ff onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards b1410eaf onsuccess: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new ecbecea0 onsuccess: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new e393657b onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new f8480a7b onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new e5191aee force: #69: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-c [...] new 377b7004 onsuccess: #70: 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 (474813ee) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_vect-spec2k6/ll [...]
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: