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 9d5928b69 0: update: glibc-ace9e3edbca62d978b1e8f392d8a5d78500272d9: 7 new 156f4a9b1 0: update: linux-6bfb56e93bcef41859c2d5ab234ffd80b691be35: 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 (9d5928b69) \ 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 1588 -> 1588 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 29312 -> 29048 bytes 05-build_abe-stage1/console.log.xz | Bin 92208 -> 92312 bytes 07-build_abe-linux/console.log.xz | Bin 10688 -> 8672 bytes 08-build_abe-glibc/console.log.xz | Bin 233168 -> 230556 bytes 09-build_abe-stage2/console.log.xz | Bin 224512 -> 224852 bytes 10-build_abe-gdb/console.log.xz | Bin 34440 -> 34400 bytes 11-build_abe-qemu/console.log.xz | Bin 32772 -> 32808 bytes 12-check_regression/console.log.xz | Bin 416 -> 416 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 6 +++--- 12 files changed, 4 insertions(+), 4 deletions(-)