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 7b38d5681 2: update: gdb-51911bd6e91ca4594424b243bfd1d2b501706abe: 5 new 9f95ce3ad 2: update: binutils-gcc-linux-glibc-gdb-qemu: 5
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 (7b38d5681) \ 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 -> 1584 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 43836 -> 44944 bytes 05-build_abe-stage1/console.log.xz | Bin 72428 -> 71236 bytes 07-build_abe-linux/console.log.xz | Bin 10420 -> 8500 bytes 08-build_abe-glibc/console.log.xz | Bin 233888 -> 236064 bytes 09-build_abe-stage2/console.log.xz | Bin 201624 -> 200992 bytes 10-build_abe-gdb/console.log.xz | Bin 42148 -> 41356 bytes 12-check_regression/console.log.xz | Bin 416 -> 416 bytes 13-update_baseline/console.log | 33 +++++++++++++++++++++++++++++++-- jenkins/manifest.sh | 17 +++++++++++------ 11 files changed, 42 insertions(+), 8 deletions(-)