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/release-arm in repository toolchain/ci/base-artifacts.
discards fa4e16392 0: update: binutils-45be8a2b16687d782c70eb3f333ef9448d54969b: 7 new 986cc3613 0: update: gdb-45be8a2b16687d782c70eb3f333ef9448d54969b: 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 (fa4e16392) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/release- [...]
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 1508 -> 1588 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 41972 -> 41900 bytes 05-build_abe-stage1/console.log.xz | Bin 86720 -> 86672 bytes 07-build_abe-linux/console.log.xz | Bin 10460 -> 10512 bytes 08-build_abe-glibc/console.log.xz | Bin 281484 -> 282364 bytes 09-build_abe-stage2/console.log.xz | Bin 220896 -> 220284 bytes 10-build_abe-gdb/console.log.xz | Bin 38528 -> 40784 bytes 11-build_abe-qemu/console.log.xz | Bin 30060 -> 30552 bytes 12-check_regression/console.log.xz | Bin 416 -> 420 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 8 ++++---- 12 files changed, 5 insertions(+), 5 deletions(-)