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 f6614ca0 0: update: linux-2f111a6fd5b5297b4e92f53798ca086f7c7d33a4: 7 new 215ba532 0: update: qemu-4c127fdbe81d66e7cafed90908d0fd1f6f2a6cd0: 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 (f6614ca0) \ 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 1524 -> 1484 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 42880 -> 42664 bytes 05-build_abe-stage1/console.log.xz | Bin 91504 -> 91656 bytes 07-build_abe-linux/console.log.xz | Bin 8952 -> 11116 bytes 08-build_abe-glibc/console.log.xz | Bin 228156 -> 228232 bytes 09-build_abe-stage2/console.log.xz | Bin 224736 -> 225432 bytes 10-build_abe-gdb/console.log.xz | Bin 40892 -> 41024 bytes 11-build_abe-qemu/console.log.xz | Bin 31164 -> 30380 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(-)