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-master-aarch64-mainline-allyesconfig in repository toolchain/ci/base-artifacts.
discards 103da1bc 4: update: binutils-gcc-linux-qemu: 33 new 9d6b02a5 4: update: binutils-gcc-linux-qemu: 33
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 (103da1bc) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-aarch6 [...]
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 1680 -> 1644 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 31296 -> 30484 bytes 04-build_abe-stage1/console.log.xz | Bin 72392 -> 73500 bytes 05-build_abe-qemu/console.log.xz | Bin 31808 -> 31236 bytes 06-build_linux/console.log.xz | Bin 4912 -> 5120 bytes 08-check_regression/console.log.xz | Bin 476 -> 472 bytes 09-update_baseline/console.log | 56 +++++++++++++++++------------------ jenkins/manifest.sh | 22 +++++++------- 9 files changed, 39 insertions(+), 39 deletions(-)