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-cpu2017rate/gnu-arm-master-O3 in repository toolchain/ci/base-artifacts/tcwg_bmk-code_vect-cpu2017rate/gnu-arm-master-O3.

discards cf799d561 onsuccess: #82: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 593e4f2bb onsuccess: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards a88a37a17 onsuccess: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards ac537ed62 onsuccess: #78: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 01f97e269 onsuccess: #78: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 5ac1bf1db onsuccess: #79: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 391e733e3 onsuccess: #81: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new d9f13971c onsuccess: #82: 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 (cf799d561) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_vect-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 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: