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-arm-next-allyesconfig in repository toolchain/ci/base-artifacts.

discards 98295a473 2: update: binutils-gcc-linux-qemu: 19975 new f5656da49 2: update: binutils-gcc-linux-qemu: 19975

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 (98295a473) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-n [...]

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 1608 -> 1556 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 42204 -> 41584 bytes 04-build_abe-stage1/console.log.xz | Bin 85792 -> 85848 bytes 05-build_abe-qemu/console.log.xz | Bin 29944 -> 29576 bytes 06-build_linux/console.log.xz | Bin 3580 -> 3572 bytes 08-check_regression/console.log.xz | Bin 484 -> 480 bytes 09-update_baseline/console.log | 307 +++++++++++++---------------------- jenkins/manifest.sh | 20 +-- 9 files changed, 119 insertions(+), 208 deletions(-)