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/release-arm in repository toolchain/ci/base-artifacts.
discards 95aaa0f20 0: update: binutils-gcc-linux-glibc-gdb: 6 new a02dceb5b 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 (95aaa0f20) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/release [...]
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 1544 -> 1572 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2776 bytes 04-build_abe-binutils/console.log.xz | Bin 63800 -> 64840 bytes 05-build_abe-gcc/console.log.xz | Bin 223592 -> 223424 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 9248 -> 9044 bytes 08-build_abe-glibc/console.log.xz | Bin 296744 -> 299156 bytes 09-build_abe-gdb/console.log.xz | Bin 50456 -> 50540 bytes 10-check_regression/console.log.xz | Bin 400 -> 400 bytes 11-update_baseline/console.log | 16 ++++++++-------- jenkins/manifest.sh | 18 +++++++++--------- 11 files changed, 17 insertions(+), 17 deletions(-)