This is an automated email from the git hooks/post-receive script.
bernie.ogden pushed a change to branch bernie/jenkmarking-multinode in repository toolchain/abe.
discards 7660083 wip: extra debugging info discards 081d739 Write exit code before inviting host to read it discards c93f133 Remove broken subprocess handling discards 0dfbf96 Make an error message more sensible discards e655af4 Remove last listener new c5af45f Remove last listener new c512b2e Make an error message more sensible new 637a6c7 Remove broken subprocess handling new 5c2b713 Write exit code before inviting host to read it new 7ae2e70 wip: extra debugging info
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 (7660083) \ N -- N -- N refs/heads/bernie/jenkmarking-multinode (7ae2e70)
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: scripts/runbenchmark.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)