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 84bd2c3 Terminate target if host isn't ready in 1 hour discards e14500a Terminate target on host exit discards 29eed88 Shut down host and target on error new 52eba7b Shut down host and target on error new eb7945c Terminate target on host exit new f457e20 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 (84bd2c3) \ N -- N -- N refs/heads/benchmarking-sync-harden (f457e20)
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 3 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: scripts/runbenchmark.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)