This is an automated email from the git hooks/post-receive script.
bernie.ogden pushed a change to branch bernie/benchmarking-clang-gcc-coremark-pro in repository toolchain/abe.
omits 6798be5 benchmark.sh: Rename GCC to something more generic omits c54c9e2 Clean up toolchain usage omits de6e3f7 Ensure that unset params get value None omits 5e430a9 WIP: Disable netctl for Juno omits e46c159 WIP: Remove tag restrictions new 0794458 Ensure that unset params get value None new 966db2e Clean up toolchain usage new 790d41c benchmark.sh: Rename GCC to something more generic new 8552c6a Disable tag limits for this run only
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 (6798be5) \ N -- N -- N refs/heads/bernie/benchmarking-clang-gcc-coremark-pro (8552c6a)
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 4 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: config/bench/boards/juno-a53.conf | 2 +- config/bench/boards/juno-a57.conf | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)