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 ba161488 0: update: glibc-f545ad4928fa1f27a3075265182b38a4f939a5f7: 7 new 474e94ed 0: update: linux-0c947b893d69231a9add855939da7c66237ab44f: 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 (ba161488) \ 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 1528 -> 1508 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 29640 -> 29628 bytes 05-build_abe-stage1/console.log.xz | Bin 72712 -> 72636 bytes 07-build_abe-linux/console.log.xz | Bin 10736 -> 9068 bytes 08-build_abe-glibc/console.log.xz | Bin 237224 -> 235904 bytes 09-build_abe-stage2/console.log.xz | Bin 199844 -> 199768 bytes 10-build_abe-gdb/console.log.xz | Bin 34252 -> 34292 bytes 11-build_abe-qemu/console.log.xz | Bin 32000 -> 31808 bytes 12-check_regression/console.log.xz | Bin 416 -> 416 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 8 ++++---- 12 files changed, 5 insertions(+), 5 deletions(-)