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

bernie.ogden pushed a change to branch benchmarking-sync-harden in repository toolchain/abe.

discards 9b37f37 Terminate target if host isn't ready in 1 hour discards be351ef Terminate target on host exit discards 7c22db5 Shut down host and target on error discards 1a66321 Simplify exit code tests discards 4c1ea26 Harden synchronization new 8aa8cf4 Harden synchronization new 5736b1d Simplify exit code tests new 5741eb3 Shut down host and target on error new 080ae36 Terminate target on host exit new c93b9ff Terminate target if host isn't ready in 1 hour

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 (9b37f37) \ N -- N -- N refs/heads/benchmarking-sync-harden (c93b9ff)

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 5 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, 5 insertions(+), 4 deletions(-)