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-cpu2017fast/llvm-aarch64-master-Os in repository toolchain/ci/base-artifacts/tcwg_bmk-code_size-cpu2017fast/llvm-aarch64-master-Os.

discards db5edd8e onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 18fc293a onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 0f7e3574 onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 0628c881 onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new bb768c13 onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 8d5f28aa onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 2167a067 onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 6311bfce onsuccess: #73: 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 (db5edd8e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_size-cpu2017fas [...]

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: