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/llvm-arm-master-Os_LTO in repository toolchain/ci/base-artifacts/tcwg_bmk-code_size-spec2k6/llvm-arm-master-Os_LTO.
discards f6a0c075 onsuccess: #75: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards e1ef750f onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 96d1ec3f onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 8fe703b5 onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new e4ec8e43 onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new d3f4390a onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new c022ca4c onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 2c58bb98 onsuccess: #75: 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 (f6a0c075) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_size-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 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: