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 0e6ff85c 0: update: glibc-a78e6a10d0b50d0ca80309775980fc99944b1727: 7 new 12d45b50 0: update: linux-feb7a43de5ef625ad74097d8fd3481d5dbc06a59: 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 (0e6ff85c) \ 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 1528 -> 1572 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 29484 -> 29644 bytes 05-build_abe-stage1/console.log.xz | Bin 72748 -> 72700 bytes 07-build_abe-linux/console.log.xz | Bin 12196 -> 9424 bytes 08-build_abe-glibc/console.log.xz | Bin 237040 -> 235380 bytes 09-build_abe-stage2/console.log.xz | Bin 199720 -> 198732 bytes 10-build_abe-gdb/console.log.xz | Bin 34188 -> 34228 bytes 11-build_abe-qemu/console.log.xz | Bin 31948 -> 32328 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(-)