This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk_llvm_apm in repository toolchain/ci/interesting-commits.
discards f2798f4 Add regression b4ee29a4450a88a64d99db0e49bac2e8670e086b from [...] discards e7873b2 Add last-good 96f842cbdb37bb84fb1bab914304a3eff152ad0d from h [...] new bc044cb Add last-good db00336a49707327552e678b59da8e85384bdae6 from h [...]
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 (f2798f4) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk_llvm_apm (bc044cb)
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: binutils | 2 -- gcc | 1 + 2 files changed, 1 insertion(+), 2 deletions(-) delete mode 100644 binutils create mode 100644 gcc