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 28d6456df 0: update: linux-6761a0ae9895fce67536510396bfa63158b0b8ec: 7 new 14c7720ef 0: update: qemu-30bd1db58b09c12b68c35f041f919014b885482d: 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 (28d6456df) \ 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 1484 -> 1524 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 43524 -> 43460 bytes 05-build_abe-stage1/console.log.xz | Bin 91396 -> 91548 bytes 07-build_abe-linux/console.log.xz | Bin 8952 -> 10880 bytes 08-build_abe-glibc/console.log.xz | Bin 227852 -> 227804 bytes 09-build_abe-stage2/console.log.xz | Bin 223360 -> 223840 bytes 10-build_abe-gdb/console.log.xz | Bin 41140 -> 41096 bytes 11-build_abe-qemu/console.log.xz | Bin 31292 -> 30212 bytes 12-check_regression/console.log.xz | Bin 416 -> 432 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 8 ++++---- 12 files changed, 5 insertions(+), 5 deletions(-)