This is an automated email from the git hooks/post-receive script.

"Diana Picus pushed a change to branch diana/docker-bmk%wip in repository toolchain/bmk-scripts.

discards c509e92 run.sh: Use different path to perf binary discards eae649f Use nodename instead of board type discards 21ed0f8 Hack around guess-board-type for arm32 discards 3c02d83 Dump cpupower frequency-info discards 37b3a08 Temporarily hack around --guess-board-type discards 52ef2b8 prepare-board.sh: More verbose error message new 63fb31f run.sh: Use nodename instead of guessing board type new 9f504db run.sh: Use different path to perf binary new b74d2d5 run.sh: Replace benchmark.sh with prepare-board.sh new 8d98541 prepare-board.sh: Create link to cpupower

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 (c509e92) \ N -- N -- N refs/heads/diana/docker-bmk%wip (8d98541)

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: prepare-board.sh | 19 +++++++++++++++++-- run.sh | 9 +++++---- 2 files changed, 22 insertions(+), 6 deletions(-)