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-Oz_LTO in repository toolchain/ci/base-artifacts/tcwg_bmk-code_size-spec2k6/llvm-arm-master-Oz_LTO.

discards 776d20386 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards 27ff73daa onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards c19a3fe17 onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] discards d83cd2747 onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 87d54bdee onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 16eff354f onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 0ffdd65f1 onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...] new 6cef40eb5 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 (776d20386) \ 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: