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-aarch64 in repository toolchain/ci/base-artifacts.
discards 637b404d 0: update: linux-316346243be6df12799c0b64b788e06bad97c30b: 7 new d9107f94 0: update: qemu-7d79344d4fa44e520e6e89f8fed9a27d3d554a9b: 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 (637b404d) \ 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 1720 -> 1492 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 42888 -> 43100 bytes 05-build_abe-stage1/console.log.xz | Bin 72772 -> 72816 bytes 07-build_abe-linux/console.log.xz | Bin 9700 -> 11736 bytes 08-build_abe-glibc/console.log.xz | Bin 232932 -> 232796 bytes 09-build_abe-stage2/console.log.xz | Bin 191300 -> 192092 bytes 10-build_abe-gdb/console.log.xz | Bin 41052 -> 40796 bytes 11-build_abe-qemu/console.log.xz | Bin 31820 -> 31104 bytes 12-check_regression/console.log.xz | Bin 388 -> 388 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 8 ++++---- 12 files changed, 5 insertions(+), 5 deletions(-)