This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 94baa8bc7 0: update: binutils-242fe37867ce33d8f8158bc2ee154d1e2e026a49: 6 new e90cebd6d 0: update: gdb-242fe37867ce33d8f8158bc2ee154d1e2e026a49: 6
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 (94baa8bc7) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...]
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 1476 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 52696 -> 51628 bytes 05-build_abe-gcc/console.log.xz | Bin 199488 -> 198184 bytes 07-build_abe-linux/console.log.xz | Bin 11992 -> 11528 bytes 08-build_abe-glibc/console.log.xz | Bin 236464 -> 233564 bytes 09-build_abe-gdb/console.log.xz | Bin 42968 -> 44560 bytes 10-check_regression/console.log.xz | Bin 416 -> 416 bytes 11-update_baseline/console.log | 4 ++-- jenkins/manifest.sh | 8 ++++---- 10 files changed, 6 insertions(+), 6 deletions(-)