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 2d1fcbb6 0: update: gdb-ff66e8c5bee8a57b531515342e6126782ea9a651: 7 new 581f83f3 0: update: glibc-7de501f9418bf099e7104b63b0e4423257981b14: 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 (2d1fcbb6) \ 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 1500 -> 1520 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 29636 -> 29472 bytes 05-build_abe-stage1/console.log.xz | Bin 91412 -> 92004 bytes 07-build_abe-linux/console.log.xz | Bin 11356 -> 11356 bytes 08-build_abe-glibc/console.log.xz | Bin 228440 -> 230184 bytes 09-build_abe-stage2/console.log.xz | Bin 221896 -> 222512 bytes 10-build_abe-gdb/console.log.xz | Bin 37176 -> 34360 bytes 11-build_abe-qemu/console.log.xz | Bin 32068 -> 31980 bytes 12-check_regression/console.log.xz | Bin 416 -> 416 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 8 ++++---- 12 files changed, 5 insertions(+), 5 deletions(-)