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/gnu-aarch64-master-O3_LTO in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO.

discards 2209a227 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 6e7cba60 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 049bdfba 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...] discards 77affd09 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...] new 058a7a12 onsuccess: #387: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new e0e84b39 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...] new 8f46c176 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new cc288f15 onsuccess: #77: 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 (2209a227) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-spec2k6/g [...]

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: