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 6054a436 0: update: gcc-c3d2600cfb476e576fd27f3f29f49e968e86774d: 7 new e2d6b456 0: update: gdb-4694a0e5fe233c5a33f0e4e4b99c9c92021b8c88: 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 (6054a436) \ 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 1680 -> 1600 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 29956 -> 29864 bytes 05-build_abe-stage1/console.log.xz | Bin 91636 -> 92844 bytes 07-build_abe-linux/console.log.xz | Bin 11992 -> 11704 bytes 08-build_abe-glibc/console.log.xz | Bin 231364 -> 231244 bytes 09-build_abe-stage2/console.log.xz | Bin 223472 -> 224360 bytes 10-build_abe-gdb/console.log.xz | Bin 34544 -> 37592 bytes 11-build_abe-qemu/console.log.xz | Bin 33768 -> 34120 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(-)