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-allmodconfig in repository toolchain/ci/base-artifacts.
discards 4a1430aee 0: reset: linux-2ce1b21cb3326e12af3c72c47e1d294b19d73947: boot new 36b36a423 0: update: linux-58da0d84fdd2563939dafa48334e190fad1b536c: boot
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 (4a1430aee) \ 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 1596 -> 1628 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 42672 -> 42660 bytes 04-build_abe-stage1/console.log.xz | Bin 69276 -> 69060 bytes 05-build_abe-qemu/console.log.xz | Bin 31108 -> 31288 bytes 06-build_linux/console.log.xz | Bin 3468 -> 3412 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 412 -> 412 bytes 09-update_baseline/console.log | 20 ++++++++++---------- jenkins/manifest.sh | 10 +++++----- reset-baseline | 0 11 files changed, 15 insertions(+), 15 deletions(-) delete mode 100644 reset-baseline