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 037faff4 2: update: binutils-gcc-linux-glibc-gdb-qemu: 4 new 410901fa 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 (037faff4) \ 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 1800 -> 1616 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 31840 -> 30144 bytes 05-build_abe-stage1/console.log.xz | Bin 90540 -> 90864 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8812 -> 8832 bytes 08-build_abe-glibc/console.log.xz | Bin 233908 -> 233216 bytes 09-build_abe-stage2/console.log.xz | Bin 190920 -> 191996 bytes 12-check_regression/console.log.xz | Bin 416 -> 420 bytes 13-update_baseline/console.log | 46 +++++++++++++++++------------------ jenkins/manifest.sh | 22 ++++++++--------- 11 files changed, 34 insertions(+), 34 deletions(-)