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 94fbb2b Correct comment about toolchain req for prebuilt case discards 94d3d38 Add xz-utils to host deps discards 3f1929a On early failure, report completion to host discards 29c043e Be more space efficient with host tarball extraction discards a6da36b Be more space efficient with target tarball extraction new 2bc136c Be more space efficient with target tarball extraction new 5bb9e50 Be more space efficient with host tarball extraction new 992fa44 On early failure, report completion to host new 942d221 Add xz-utils to host deps new ca3e04a Correct comment about toolchain req for prebuilt case
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 (94fbb2b) \ N -- N -- N refs/heads/bernie/benchmarking (ca3e04a)
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 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)