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-arm in repository toolchain/ci/base-artifacts.

discards e1700585 0: update: gdb-d65edaa0bc3f24537ecde3735b1fa041f36f4ab8: 6 new b0ba1f04 0: update: glibc-ac8047cdf326504f652f7db97ec96c0e0cee052f: 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 (e1700585) \ 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 1744 -> 1552 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50424 -> 50820 bytes 05-build_abe-gcc/console.log.xz | Bin 233592 -> 234524 bytes 07-build_abe-linux/console.log.xz | Bin 11036 -> 11024 bytes 08-build_abe-glibc/console.log.xz | Bin 232196 -> 232156 bytes 09-build_abe-gdb/console.log.xz | Bin 48944 -> 45956 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(-)