This is an automated email from the git hooks/post-receive script.
bernie.ogden pushed a change to branch benchmarking-fixes in repository toolchain/abe.
discards 1ef1bbe Benchmark.sh: User-specified general metadata discards b232991 Benchmark.sh: Helpful message when metadata is unset discards d16cade Add more information about binaries to build.log discards 890c80c Improve binaries function discards 357956a Create function to return list of binaries discards 2fca91d Dump abe source info into build.log adds 29f9f4b Benchmark.sh: Helpful message when metadata is unset adds b8008ce Benchmark.sh: User-specified general metadata new f0c71fd Dump abe source info into build.log new 21ca06a Create function to return list of binaries new 1960aa4 Improve binaries function new a79946f Add more information about binaries to build.log
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 (1ef1bbe) \ N -- N -- N refs/heads/benchmarking-fixes (a79946f)
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.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)