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 5a24344 WIP discards fc4b6c6 WIP: 'Semi-trusted' concept, for testing purposes discards b1a11a1 Add trusted-host-session.yaml discards 8c85bc4 Remove redundant exit from remote_exec_async discards 6fa81c4 Add some standard settings to target-session new a3f0ce4 Add some standard settings to target-session new 1c927d5 Remove redundant exit from remote_exec_async new c5b47c0 Add trusted-host-session.yaml new adc04b0 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 (5a24344) \ N -- N -- N refs/heads/bernie/benchmarking-uinstance (adc04b0)
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 | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-)