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-next-allyesconfig in repository toolchain/ci/base-artifacts.
discards 8a617ba4 0: update: linux-18d70724d5498d465f396282a59e59f0f4c7e2ca: all new 28fc952d 0: update: linux-18d70724d5498d465f396282a59e59f0f4c7e2ca: all
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 (8a617ba4) \ 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 1620 -> 1576 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30040 -> 29316 bytes 04-build_abe-stage1/console.log.xz | Bin 69704 -> 68408 bytes 05-build_abe-qemu/console.log.xz | Bin 32156 -> 31676 bytes 06-build_linux/console.log.xz | Bin 3728 -> 3100 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 412 -> 412 bytes 09-update_baseline/console.log | 18 +++++++++--------- jenkins/manifest.sh | 4 ++-- 10 files changed, 11 insertions(+), 11 deletions(-)