This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 3e5e50a0 0: update: glibc-41a11a5e83265c7718787b9cfb8b3c109c59b980: 7 new d0b17e0c 0: update: linux-a33f5c380c4bd3fa5278d690421b72052456d9fe: 7
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 (3e5e50a0) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]
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 1604 -> 1532 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 29656 -> 29632 bytes 05-build_abe-stage1/console.log.xz | Bin 72804 -> 72720 bytes 07-build_abe-linux/console.log.xz | Bin 11076 -> 8920 bytes 08-build_abe-glibc/console.log.xz | Bin 236776 -> 234768 bytes 09-build_abe-stage2/console.log.xz | Bin 199176 -> 198936 bytes 10-build_abe-gdb/console.log.xz | Bin 34256 -> 34136 bytes 11-build_abe-qemu/console.log.xz | Bin 31944 -> 31916 bytes 12-check_regression/console.log.xz | Bin 416 -> 416 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 6 +++--- 12 files changed, 4 insertions(+), 4 deletions(-)