This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts.
discards 102735646 2: update: binutils-gcc-linux-qemu: 20497 new b3be28699 2: update: binutils-gcc-linux-qemu: 20676
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 (102735646) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-aarch [...]
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 1 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: 01-reset_artifacts/console.log.xz | Bin 1568 -> 1564 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30080 -> 30408 bytes 04-build_abe-stage1/console.log.xz | Bin 68196 -> 68672 bytes 05-build_abe-qemu/console.log.xz | Bin 32764 -> 32548 bytes 06-build_linux/console.log.xz | Bin 6052 -> 18600 bytes 08-check_regression/console.log.xz | Bin 476 -> 484 bytes 09-update_baseline/console.log | 222 +++++++++++++++++------------------ jenkins/manifest.sh | 20 ++-- results | 2 +- 10 files changed, 122 insertions(+), 122 deletions(-)