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-arm in repository toolchain/ci/base-artifacts.
discards 00615b34 2: update: binutils-gcc-linux-glibc-gdb-qemu: 4 new 3860a3f8 2: update: binutils-gcc-linux-glibc-gdb-qemu: 4
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 (00615b34) \ 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 1640 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 30148 -> 30928 bytes 05-build_abe-stage1/console.log.xz | Bin 91356 -> 91468 bytes 07-build_abe-linux/console.log.xz | Bin 8680 -> 8648 bytes 08-build_abe-glibc/console.log.xz | Bin 233600 -> 232744 bytes 09-build_abe-stage2/console.log.xz | Bin 191436 -> 191960 bytes 12-check_regression/console.log.xz | Bin 416 -> 416 bytes 13-update_baseline/console.log | 142 +++++++++++++++++------------------ jenkins/manifest.sh | 16 ++-- 10 files changed, 79 insertions(+), 79 deletions(-)