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

discards 38b9e6bd 0: update: linux-ff3821bc355275ada757dd2be8654dd0aae9c2f9: all new 8c09565e 0: reset: linux-ff3821bc355275ada757dd2be8654dd0aae9c2f9: 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 (38b9e6bd) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/gnu-release-arm-n [...]

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 1684 -> 1608 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 29200 -> 29340 bytes 04-build_abe-stage1/console.log.xz | Bin 87624 -> 87684 bytes 05-build_abe-qemu/console.log.xz | Bin 33872 -> 33592 bytes 06-build_linux/console.log.xz | Bin 3580 -> 3488 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 412 -> 412 bytes 09-update_baseline/console.log | 16 ++++++++-------- jenkins/manifest.sh | 8 ++++---- reset-baseline | 0 11 files changed, 12 insertions(+), 12 deletions(-) create mode 100644 reset-baseline