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-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts.

discards da85cea3 2: update: binutils-169a28718130b39010564185fbe64e4ce6fbf4d1: 19812 new 74a306fd 2: update: qemu-d1fe59377bbbf91dfded1f08ffe3c636e9db8dc0: 19812

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 (da85cea3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-master-arm-ma [...]

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 1608 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 43080 -> 42224 bytes 04-build_abe-stage1/console.log.xz | Bin 91072 -> 91180 bytes 05-build_abe-qemu/console.log.xz | Bin 31664 -> 30144 bytes 06-build_linux/console.log.xz | Bin 5840 -> 5780 bytes 08-check_regression/console.log.xz | Bin 540 -> 540 bytes 09-update_baseline/console.log | 100 +++++++++++++++++------------------ jenkins/manifest.sh | 10 ++-- 9 files changed, 55 insertions(+), 55 deletions(-)