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 2676e939 0: update: binutils-34630bd307d358b35078c0696a204edb25d938b3: 7 new 5007fb9a 0: update: gcc-0b8464365b15ac108cd1d00d5bc56d229c1340de: 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 (2676e939) \ 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 1668 -> 1528 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 31168 -> 29592 bytes 05-build_abe-stage1/console.log.xz | Bin 73552 -> 71140 bytes 07-build_abe-linux/console.log.xz | Bin 12564 -> 12620 bytes 08-build_abe-glibc/console.log.xz | Bin 234832 -> 234568 bytes 09-build_abe-stage2/console.log.xz | Bin 200348 -> 197104 bytes 10-build_abe-gdb/console.log.xz | Bin 35316 -> 35220 bytes 11-build_abe-qemu/console.log.xz | Bin 31696 -> 31960 bytes 12-check_regression/console.log.xz | Bin 416 -> 416 bytes 13-update_baseline/console.log | 2 +- jenkins/manifest.sh | 10 +++++----- 12 files changed, 6 insertions(+), 6 deletions(-)