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_size-spec2k6/gnu-aarch64-master-O2 in repository toolchain/ci/base-artifacts/tcwg_bmk-code_size-spec2k6/gnu-aarch64-master-O2.
discards 196301af force: #90: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk-c [...] discards 437dcccc onsuccess: #88: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 1a2534c8 onsuccess: #85: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 82712b95 onsuccess: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 5262b81c onsuccess: #78: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new cbfd3eb8 onsuccess: #78: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 93937795 onsuccess: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 99e9b4c2 onsuccess: #85: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new e3e8fbd6 onsuccess: #88: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new e8e70cc6 force: #90: 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 (196301af) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_size-spec2k6/gn [...]
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: