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 7dbc12d0 0: update: glibc-6ff3c7714900529b8f5ca64b58d5da9cd5d5b345: 7 new 6d7f44ac 0: update: linux-3123109284176b1532874591f7c81f3837bbdc17: 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 (7dbc12d0) \ 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 1724 -> 1540 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 29500 -> 29256 bytes 05-build_abe-stage1/console.log.xz | Bin 92448 -> 92228 bytes 07-build_abe-linux/console.log.xz | Bin 10824 -> 8968 bytes 08-build_abe-glibc/console.log.xz | Bin 233176 -> 230928 bytes 09-build_abe-stage2/console.log.xz | Bin 224288 -> 226208 bytes 10-build_abe-gdb/console.log.xz | Bin 34660 -> 34700 bytes 11-build_abe-qemu/console.log.xz | Bin 32348 -> 32272 bytes 12-check_regression/console.log.xz | Bin 432 -> 416 bytes 13-update_baseline/console.log | 14 +++++++------- jenkins/manifest.sh | 6 +++--- 12 files changed, 10 insertions(+), 10 deletions(-)