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 986cc3613 0: update: gdb-45be8a2b16687d782c70eb3f333ef9448d54969b: 7 new d0676c0d8 0: update: glibc-5abb1c32c22145c9e01307910fa2f82adf85d3ee: 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 (986cc3613) \ 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 1588 -> 1604 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 41900 -> 42060 bytes 05-build_abe-stage1/console.log.xz | Bin 86672 -> 86804 bytes 07-build_abe-linux/console.log.xz | Bin 10512 -> 10484 bytes 08-build_abe-glibc/console.log.xz | Bin 282364 -> 285240 bytes 09-build_abe-stage2/console.log.xz | Bin 220284 -> 220844 bytes 10-build_abe-gdb/console.log.xz | Bin 40784 -> 37880 bytes 11-build_abe-qemu/console.log.xz | Bin 30552 -> 30336 bytes 12-check_regression/console.log.xz | Bin 420 -> 416 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 6 +++--- 12 files changed, 4 insertions(+), 4 deletions(-)