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-O3 in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/llvm-aarch64-master-O3.
discards b01db8f3e onsuccess: #111: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 1f3d6756f onsuccess: #110: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards e6c61b09b onsuccess: #102: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards dafc1aea4 force: #101: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] new 6436a99cb force: #101: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] new 4401770ed onsuccess: #102: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 7c127ab3c onsuccess: #110: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new dd687b981 onsuccess: #111: 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 (b01db8f3e) \ 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: