This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts.
discards a9c4f5dc2 linux-7566ec393f4161572ba6f11ad5171fd5d59b0fbd: 10524 new 7c4ec59e1 linux-62393dbcbe0f3001691e4bd479a25beb5941f2ed: 10524
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 (a9c4f5dc2) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_kernel/llvm-release-arm- [...]
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: 1-reset_artifacts/console.log | 78 +- 2-build_llvm/console.log | 9864 +- 2-build_llvm/revision | 1 - 3-count_linux_objs/console.log | 524136 +++++++++++++++++++------------------ 3-count_linux_objs/revision | 1 - 4-check_regression/console.log | 2 +- 5-update_baseline/console.log | 4 +- console.log | 533204 +++++++++++++++++++------------------- distance-to-baseline | 2 +- jenkins/build-name | 2 +- jenkins/manifest.sh | 10 +- trigger-bisect-on-failure | 4 +- 12 files changed, 533730 insertions(+), 533578 deletions(-) delete mode 100644 2-build_llvm/revision delete mode 100644 3-count_linux_objs/revision