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 0e88d4202 0: update: gcc-f2572a398d21fd52435c94065c0651fd79db847c: 7 new 77a11b3ae 0: update: glibc-824dd3ec4922fbb9a34c62f4829e7817cc60e29a: 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 (0e88d4202) \ 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 1552 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 04-build_abe-binutils/console.log.xz | Bin 43496 -> 43556 bytes 05-build_abe-stage1/console.log.xz | Bin 90828 -> 92008 bytes 07-build_abe-linux/console.log.xz | Bin 11408 -> 11140 bytes 08-build_abe-glibc/console.log.xz | Bin 228944 -> 229904 bytes 09-build_abe-stage2/console.log.xz | Bin 217416 -> 220032 bytes 10-build_abe-gdb/console.log.xz | Bin 41228 -> 41244 bytes 11-build_abe-qemu/console.log.xz | Bin 30812 -> 30708 bytes 12-check_regression/console.log.xz | Bin 416 -> 416 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 8 ++++---- 12 files changed, 5 insertions(+), 5 deletions(-)