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 db9cc37 Terminate target if host isn't ready in 1 hour discards ebf73ce Terminate target on host exit discards 5a03cf6 Shut down host and target on error discards 3441be8 Simplify exit code tests discards e502081 Harden synchronization new 4c1ea26 Harden synchronization new 1a66321 Simplify exit code tests new 7c22db5 Shut down host and target on error new be351ef Terminate target on host exit new 9b37f37 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 (db9cc37) \ N -- N -- N refs/heads/benchmarking-sync-harden (9b37f37)
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/host-session | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)