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

bernie.ogden pushed a change to branch bernie/benchmarking-uinstance-arbitrary in repository toolchain/abe.

discards 1370ce4 Create multilib and non-multilib host-session yaml discards bf2ee06 Template for use in trusted LAVA uinstance discards 6da8b78 Add missing tcpdump dependency discards a76c20b Permit host machine to be of any type discards 840f31b Benchmark.sh: Support mustang host/target discards 3e48ec5 Benchmark.sh: Support deploy_linaro_kernel discards bc48c50 Remove redundant specialised target-session-*.yaml new 272fa53 Remove redundant specialised target-session-*.yaml new 7ca5549 Benchmark.sh: Support deploy_linaro_kernel new e5ad39f Benchmark.sh: Support mustang host/target new ecbf1a1 Permit host machine to be of any type new cb7abb3 Add missing tcpdump dependency new 84a6a2c Template for use in trusted LAVA uinstance new bec6374 Create multilib and non-multilib host-session yaml

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 (1370ce4) \ N -- N -- N refs/heads/bernie/benchmarking-uinstance-arbitrary (bec6374)

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 7 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: scripts/Benchmark.sh | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-)