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 d4231ca Stop pinging on removal of target dir discards 8bea2e5 Echo all commands in Benchmark.job discards a09d2f5 Write/read pid of sleeper in file discards 8d7f93e wip: debugging printfs new 31a82c54 Write/read pid of sleeper in file new 68d516c Echo all commands in Benchmark.job new 067c1df Stop pinging on removal of target dir new c092629 Extend comment new 023507b Fix command to remove benchmark tarball new 843232c Use local thing rather than global prebuilt new 73bbea5 Normalize thing and report it unconditionally new 40c0503 get_thing always downloads to a tmpdir
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 (d4231ca) \ N -- N -- N refs/heads/bernie/benchmarking (40c0503)
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 8 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 | 32 +++++++++++++------------------- 1 file changed, 13 insertions(+), 19 deletions(-)