This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_embed_build/master-thumb_m3_eabi in repository toolchain/ci/base-artifacts/tcwg_gnu_embed_build/master-thumb_m3_eabi.

discards c6d76e5 onsuccess: #51: 7: [TCWG CI] https://ci.linaro.org/job/tcwg_g [...] discards e2d1d0d onsuccess: #50: 7: [TCWG CI] https://ci.linaro.org/job/tcwg_g [...] discards 502f8aa onsuccess: #49: 7: [TCWG CI] https://ci.linaro.org/job/tcwg_g [...] discards b02b832 onsuccess: #48: 7: [TCWG CI] https://ci.linaro.org/job/tcwg_g [...] discards 938867c onsuccess: #47: 7: [TCWG CI] https://ci.linaro.org/job/tcwg_g [...] new 879db98 onsuccess: #47: 7: [TCWG CI] https://ci.linaro.org/job/tcwg_g [...] new 0d30d76 onsuccess: #48: 7: [TCWG CI] https://ci.linaro.org/job/tcwg_g [...] new 1c127f2 onsuccess: #49: 7: [TCWG CI] https://ci.linaro.org/job/tcwg_g [...] new 41c65a3 onsuccess: #50: 7: [TCWG CI] https://ci.linaro.org/job/tcwg_g [...] new e8c8a66 onsuccess: #51: 7: [TCWG CI] https://ci.linaro.org/job/tcwg_g [...]

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 (c6d76e5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_embed_build/master-t [...]

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 5 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: