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

christophe.lyon pushed a change to branch fix-body in repository toolchain/gcc-compare-results.

discards 3a5b16e compare_jobs.sh: Fix HTML. discards b62f727 Bug #1919: Make it clear when logs are missing. adds ae7e47a compare_jobs.sh: Exit with status=1 in case of regression or [...] adds abeb4f9 compare_jobs.sh: Concatenate all diff-* reports after the mai [...] adds f02cb6b compare_tests: Fix usage and exit codes. compare_jobs.sh: Han [...] adds a237d2a Merge "compare_tests: Fix usage and exit codes. compare_jobs. [...] new 588fb65 Bug #1919: Make it clear when logs are missing. new b55a514 compare_jobs.sh: Fix HTML.

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 (3a5b16e) \ N -- N -- N refs/heads/fix-body (b55a514)

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: compare_jobs.sh | 43 +++++++++++++++++++++++++++++++++++-------- compare_tests | 31 ++++++++++++++----------------- 2 files changed, 49 insertions(+), 25 deletions(-)