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 e4da3e4 Dump cpupower frequency-info discards e54e5bb Revert "Temporarily disable cpu freq config" discards 51a8016 Revert "Try to get past perf -e" discards 8c808b4 Revert "Run some ls" discards 83c0e06 Try to get past perf -e discards 584383f Run some ls discards abf25f9 Temporarily disable cpu freq config discards 0e86e57 Revert "Try to find out which cpupower we use" discards a0dfa43 Try to find out which cpupower we use new 3c02d83 Dump cpupower frequency-info

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 (e4da3e4) \ N -- N -- N refs/heads/diana/docker-bmk%wip (3c02d83)

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: run.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)