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

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

discards 8e8ee0e Support makeflags in multinode jobs discards f0f254b Fix CLI-overriding of make_flags discards 10998ec Permit benchmarking with prebuilt benchmark discards 58ea108 Refactor toolchain download/install code new 3340d96 Refactor toolchain download/install code new 36eafec Permit benchmarking with prebuilt benchmark new 0a7fa86 Fix CLI-overriding of make_flags new 4da7fbb Support makeflags in multinode jobs

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 (8e8ee0e) \ N -- N -- N refs/heads/bernie/benchmarking (4da7fbb)

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: scripts/Benchmark.job | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)