This is an automated email from the git hooks/post-receive script.
bernie.ogden pushed a change to branch bernie/benchmarking-uinstance in repository toolchain/abe.
discards dca8c51 WIP: 'Semi-trusted' concept, for testing purposes discards e1ff2b2 Add trusted-host-session.yaml discards 3db4aea Support gathering of results to bundle stream new 0b563a0 Make LAVA API available in sessions from host new 8382fe4 Support gathering of results to bundle stream new 4e95458 Add trusted-host-session.yaml new 361149e WIP: 'Semi-trusted' concept, for testing purposes
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 (dca8c51) \ N -- N -- N refs/heads/bernie/benchmarking-uinstance (361149e)
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 | 4 ++++ 1 file changed, 4 insertions(+)