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 b3c530d Template for use in trusted LAVA uinstance discards 1085ca7 Remove *-multilib from host packages discards 36a4e22 Add missing tcpdump dependency discards e7ba1ab Permit host machine to be of any type discards 08b5349 target-session.yaml:Remove unused CONFIG parameter new 54e4c59 Permit host machine to be of any type new 0523df4 Add missing tcpdump dependency new 6215e40 Remove *-multilib from host packages new e23a13d Template for use in trusted LAVA uinstance

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 (b3c530d) \ N -- N -- N refs/heads/bernie/benchmarking-uinstance-arbitrary (e23a13d)

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/lava/target-session.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)