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_check_gcc/master-thumb_m7_eabi in repository toolchain/ci/base-artifacts/tcwg_gnu_embed_check_gcc/master-thumb_m7_eabi.
discards 14452b22 onsuccess: #175: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 8093b252 onsuccess: #174: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 7a4904b7 onsuccess: #172: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 31b3e24d onsuccess: #171: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards bc1f5f4d onsuccess: #169: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new d9e76b54 onsuccess: #169: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new f7554ab6 onsuccess: #171: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new cc05ec6f onsuccess: #172: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new d254c98e onsuccess: #174: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 20ed624f onsuccess: #175: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...]
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 (14452b22) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_embed_check_gcc/mast [...]
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: