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 1649a5da 0: update: binutils-45cf0dc2ecd2354c6f8e6d3f5d19f8012c97d978: 7 new 9cd98c73 0: update: gcc-1e942d7c05c66ccc477567506a6bf86d91cae429: 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 (1649a5da) \ 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 1536 -> 1620 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2788 bytes 04-build_abe-binutils/console.log.xz | Bin 30044 -> 30076 bytes 05-build_abe-stage1/console.log.xz | Bin 92152 -> 91228 bytes 07-build_abe-linux/console.log.xz | Bin 11960 -> 12240 bytes 08-build_abe-glibc/console.log.xz | Bin 229356 -> 229724 bytes 09-build_abe-stage2/console.log.xz | Bin 230756 -> 227800 bytes 10-build_abe-gdb/console.log.xz | Bin 34788 -> 34100 bytes 11-build_abe-qemu/console.log.xz | Bin 31712 -> 31484 bytes 12-check_regression/console.log.xz | Bin 416 -> 416 bytes 13-update_baseline/console.log | 12 ++++++------ jenkins/manifest.sh | 10 +++++----- 12 files changed, 11 insertions(+), 11 deletions(-)