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_v8a_hard_eabi in repository toolchain/ci/base-artifacts/tcwg_gnu_embed_check_gcc/master-thumb_v8a_hard_eabi.
discards 93469d3 onsuccess: #177: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards c216c0b onsuccess: #176: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards d36cc3e onsuccess: #175: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards e983daf onsuccess: #173: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards bbdb4fa onsuccess: #172: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new ae2c6c9 onsuccess: #172: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 01702d2 onsuccess: #173: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 7dcbf06 onsuccess: #175: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new a0973a7 onsuccess: #176: 0: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new a355097 onsuccess: #177: 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 (93469d3) \ 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: