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-arm in repository toolchain/ci/base-artifacts.

discards 6b2e225b1 2: update: gdb-1a98bb552d752d1dbedc8fdae504629d21d776f2: 5 new 2703f834a 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 (6b2e225b1) \ 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 1672 -> 1532 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2792 bytes 04-build_abe-binutils/console.log.xz | Bin 44196 -> 45164 bytes 05-build_abe-stage1/console.log.xz | Bin 91452 -> 91296 bytes 07-build_abe-linux/console.log.xz | Bin 10928 -> 8780 bytes 08-build_abe-glibc/console.log.xz | Bin 228080 -> 231264 bytes 09-build_abe-stage2/console.log.xz | Bin 224612 -> 223788 bytes 10-build_abe-gdb/console.log.xz | Bin 42484 -> 40280 bytes 12-check_regression/console.log.xz | Bin 416 -> 416 bytes 13-update_baseline/console.log | 33 +++++++++++++++++++++++++++++++-- jenkins/manifest.sh | 23 ++++++++++++++--------- 11 files changed, 45 insertions(+), 11 deletions(-)