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 66195c2f 0: update: gcc-0460ba622e833db5cc1cc793201762bbbd30af6b: 7 new de5a514e 0: update: gdb-dd09fe0d53242a5f6a86d2822b0cfdeb3f5baa8f: 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 (66195c2f) \ 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 1668 -> 1604 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30464 -> 30228 bytes 05-build_abe-stage1/console.log.xz | Bin 91248 -> 92756 bytes 07-build_abe-linux/console.log.xz | Bin 10912 -> 10888 bytes 08-build_abe-glibc/console.log.xz | Bin 232388 -> 231876 bytes 09-build_abe-stage2/console.log.xz | Bin 222796 -> 224528 bytes 10-build_abe-gdb/console.log.xz | Bin 34540 -> 38136 bytes 11-build_abe-qemu/console.log.xz | Bin 32004 -> 32392 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(-)