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

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

discards e9724ad3 0: update: gcc-7ca21601704c4a637f3cefa7c8814920782354d8: 7 new 85a5d819 0: update: glibc-716c4027b04db785034b0f67ac552cfaff360463: 7

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 (e9724ad3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]

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 1532 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 29520 -> 29628 bytes 05-build_abe-stage1/console.log.xz | Bin 71716 -> 73104 bytes 07-build_abe-linux/console.log.xz | Bin 11380 -> 11392 bytes 08-build_abe-glibc/console.log.xz | Bin 234404 -> 236336 bytes 09-build_abe-stage2/console.log.xz | Bin 199168 -> 200240 bytes 10-build_abe-gdb/console.log.xz | Bin 35348 -> 35172 bytes 11-build_abe-qemu/console.log.xz | Bin 32180 -> 32084 bytes 12-check_regression/console.log.xz | Bin 416 -> 432 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 8 ++++---- 12 files changed, 5 insertions(+), 5 deletions(-)