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-aarch64 in repository toolchain/ci/base-artifacts.
discards c547bd134 2: update: binutils-c808def421f383a226198751d93239ded2b0d21d: 0 discards e7c4569dd 1: reset: binutils-1eaa86a6d5bc8b79e1783582f5b58e4fa5675e03: 0 new beaf7645b 1: reset: gdb-96c7115a9a1669c70331f594eca40eebeb5f2d2c: 0
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 (c547bd134) \ 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 1604 -> 1532 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 16304 -> 15628 bytes 12-check_regression/console.log.xz | Bin 412 -> 412 bytes 13-update_baseline/console.log | 45 +++++++++++++++++++++++++++-------- jenkins/manifest.sh | 8 +++---- reset-baseline | 0 7 files changed, 39 insertions(+), 14 deletions(-) create mode 100644 reset-baseline