This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-mainline-allyesconfig in repository toolchain/ci/base-artifacts.
discards 490447d9c 2: update: binutils-gcc-linux-qemu: 20503 new e5d868d53 2: update: binutils-gcc-linux-qemu: 20503
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 (490447d9c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-aarch [...]
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 1560 -> 1568 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 42604 -> 43028 bytes 04-build_abe-stage1/console.log.xz | Bin 67744 -> 68152 bytes 05-build_abe-qemu/console.log.xz | Bin 30380 -> 30612 bytes 06-build_linux/console.log.xz | Bin 3460 -> 3540 bytes 08-check_regression/console.log.xz | Bin 480 -> 480 bytes 09-update_baseline/console.log | 234 +++++++++++++++++------------------ jenkins/manifest.sh | 18 +-- 9 files changed, 126 insertions(+), 126 deletions(-)