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 2e41e75 Template for use in trusted LAVA uinstance discards f747909 Remove *-multilib from host packages discards 5643e21 Add missing tcpdump dependency discards 16ed476 Permit host machine to be of any type discards b0b33f2 Do not infer device validation from triple discards 800445e Decouple triple from toolchain new 4282ec7 Decouple triple from toolchain new dbcf6fa Do not infer device validation from triple new a20143a Permit host machine to be of any type new 4caa42a Add missing tcpdump dependency new a99fd0e Remove *-multilib from host packages new 290f9b3 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 (2e41e75) \ N -- N -- N refs/heads/bernie/benchmarking-uinstance-arbitrary (290f9b3)

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 6 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/jobdefs/template-uinstance.yaml | 1 + config/bench/jobdefs/template.yaml | 1 + 2 files changed, 2 insertions(+)