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 581f83f3 0: update: glibc-7de501f9418bf099e7104b63b0e4423257981b14: 7 new e3b262aa 0: update: linux-fb3b0673b7d5b477ed104949450cd511337ba3c6: 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 (581f83f3) \ 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 1520 -> 1524 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 29472 -> 29320 bytes 05-build_abe-stage1/console.log.xz | Bin 92004 -> 91584 bytes 07-build_abe-linux/console.log.xz | Bin 11356 -> 9192 bytes 08-build_abe-glibc/console.log.xz | Bin 230184 -> 228912 bytes 09-build_abe-stage2/console.log.xz | Bin 222512 -> 221492 bytes 10-build_abe-gdb/console.log.xz | Bin 34360 -> 34340 bytes 11-build_abe-qemu/console.log.xz | Bin 31980 -> 32056 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(-)