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-cpu2017rate/llvm-arm-master-Os_LTO in repository toolchain/ci/base-artifacts/tcwg_bmk-code_size-cpu2017rate/llvm-arm-master-Os_LTO.
discards ae255df onsuccess: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards f63b42e onsuccess: #80: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards f0058fa onsuccess: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 956e384 onsuccess: #78: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 20b3b6c onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 03b1d3c onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 745a1b4 onsuccess: #78: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 423c6d0 onsuccess: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new a78b51c onsuccess: #80: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 042dd95 onsuccess: #81: 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 (ae255df) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_size-cpu2017rat [...]
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: