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 a0b4a5c2 0: update: linux-56e337f2cf1326323844927a04e9dbce9a244835: 7 new 04d4b6bd 0: update: qemu-1d60bb4b14601e38ed17384277aa4c30c57925d3: 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 (a0b4a5c2) \ 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 1580 -> 1580 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2776 bytes 04-build_abe-binutils/console.log.xz | Bin 30164 -> 30164 bytes 05-build_abe-stage1/console.log.xz | Bin 73260 -> 73068 bytes 07-build_abe-linux/console.log.xz | Bin 9172 -> 10892 bytes 08-build_abe-glibc/console.log.xz | Bin 234892 -> 234928 bytes 09-build_abe-stage2/console.log.xz | Bin 200872 -> 199812 bytes 10-build_abe-gdb/console.log.xz | Bin 35392 -> 34420 bytes 11-build_abe-qemu/console.log.xz | Bin 32488 -> 31028 bytes 12-check_regression/console.log.xz | Bin 420 -> 416 bytes 13-update_baseline/console.log | 12 ++++++------ jenkins/manifest.sh | 6 +++--- 12 files changed, 9 insertions(+), 9 deletions(-)