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 1aba5f55 0: update: gdb-acd65fa610df09a0954b8fecdadf546215263c5d: 6 new b7a7a578 0: update: glibc-2249ec60a987f9a7aa585890de2bd365b3656d28: 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 (1aba5f55) \ 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 1488 -> 1504 bytes 02-prepare_abe/console.log.xz | Bin 2704 -> 2696 bytes 04-build_abe-binutils/console.log.xz | Bin 37064 -> 36920 bytes 05-build_abe-gcc/console.log.xz | Bin 212636 -> 214512 bytes 07-build_abe-linux/console.log.xz | Bin 10540 -> 10560 bytes 08-build_abe-glibc/console.log.xz | Bin 237188 -> 238288 bytes 09-build_abe-gdb/console.log.xz | Bin 37596 -> 34340 bytes 10-check_regression/console.log.xz | Bin 416 -> 416 bytes 11-update_baseline/console.log | 36 ----------------------------------- jenkins/manifest.sh | 8 ++++---- 10 files changed, 4 insertions(+), 40 deletions(-)