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

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

discards 9c82396c 0: update: binutils-gcc-linux-glibc-gdb: 6 new 4f8fe3c7 0: update: binutils-gcc-linux-glibc-gdb: 6

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 (9c82396c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...]

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 1512 -> 1544 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 38004 -> 38028 bytes 05-build_abe-gcc/console.log.xz | Bin 211616 -> 211532 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 10012 -> 8660 bytes 08-build_abe-glibc/console.log.xz | Bin 238896 -> 240864 bytes 09-build_abe-gdb/console.log.xz | Bin 37540 -> 38192 bytes 10-check_regression/console.log.xz | Bin 416 -> 420 bytes 11-update_baseline/console.log | 16 ++++++++-------- jenkins/manifest.sh | 26 +++++++++++++------------- 11 files changed, 21 insertions(+), 21 deletions(-)