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 3860a3f8 2: update: binutils-gcc-linux-glibc-gdb-qemu: 4 new 3961bf63 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 (3860a3f8) \ 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 1660 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 30928 -> 30748 bytes 05-build_abe-stage1/console.log.xz | Bin 91468 -> 91564 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8648 -> 8884 bytes 08-build_abe-glibc/console.log.xz | Bin 232744 -> 232984 bytes 09-build_abe-stage2/console.log.xz | Bin 191960 -> 192256 bytes 12-check_regression/console.log.xz | Bin 416 -> 416 bytes 13-update_baseline/console.log | 154 +++++++++++++++++------------------ jenkins/manifest.sh | 24 +++--- 11 files changed, 89 insertions(+), 89 deletions(-)