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 4dff5018 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3b16484a 0: update: binutils-gcc-linux-glibc-gdb-qemu: 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 (4dff5018) \ 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 1556 -> 1560 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30176 -> 30596 bytes 05-build_abe-stage1/console.log.xz | Bin 71804 -> 71488 bytes 07-build_abe-linux/console.log.xz | Bin 9096 -> 9872 bytes 08-build_abe-glibc/console.log.xz | Bin 237816 -> 237848 bytes 09-build_abe-stage2/console.log.xz | Bin 201744 -> 202596 bytes 10-build_abe-gdb/console.log.xz | Bin 37300 -> 37640 bytes 11-build_abe-qemu/console.log.xz | Bin 32084 -> 32668 bytes 12-check_regression/console.log.xz | Bin 416 -> 416 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 26 +++++++++++++------------- 12 files changed, 14 insertions(+), 14 deletions(-)