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 85a5d819 0: update: glibc-716c4027b04db785034b0f67ac552cfaff360463: 7 new dd6f85f4 0: update: linux-99613159ad749543621da8238acf1a122880144e: 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 (85a5d819) \ 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 1680 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 29628 -> 29864 bytes 05-build_abe-stage1/console.log.xz | Bin 73104 -> 73268 bytes 07-build_abe-linux/console.log.xz | Bin 11392 -> 9664 bytes 08-build_abe-glibc/console.log.xz | Bin 236336 -> 235852 bytes 09-build_abe-stage2/console.log.xz | Bin 200240 -> 200476 bytes 10-build_abe-gdb/console.log.xz | Bin 35172 -> 35180 bytes 11-build_abe-qemu/console.log.xz | Bin 32084 -> 31328 bytes 12-check_regression/console.log.xz | Bin 432 -> 416 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 6 +++--- 12 files changed, 4 insertions(+), 4 deletions(-)