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

discards 26dd456c force: #139: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] discards be3d5119 force: #132: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] discards edb3d686 onsuccess: #130: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 63ace8d0 force: #128: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] new 2cc9e613 force: #128: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] new 68a201b3 onsuccess: #130: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 6d496ac5 force: #132: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...] new 7602d128 force: #139: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk- [...]

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 (26dd456c) \ 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: