This is an automated email from the git hooks/post-receive script.
bernie.ogden pushed a change to branch bernie/trust in repository toolchain/abe.
discards 66b4d7f Detect more IP resolve failure cases discards 919d105 Use getent, not dig discards eaf04e3 Strengthen check for IP resolve failure new 88683b8 host_ip can only be an IP address, don't resolve new 9503749 If we cannot resolve target, assume we have IP
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 (66b4d7f) \ N -- N -- N refs/heads/bernie/trust (9503749)
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 2 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 | 29 ++++++++++++----------------- 1 file changed, 12 insertions(+), 17 deletions(-)