This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/94/44194/3 in repository toolchain/jenkins-scripts.
discards ed9a78ec7 round-robin-notify.sh: remove finalize_mail discards 237adcafd round-robin-notify.sh: print_mail_body discards 293b7ad2c round-robin-notify.sh: generate jira files directly instead o [...] discards 23fcda0f2 round-robin-notify.sh: Add print_result print_config and use [...] discards bfab9fc06 round-robin-notify.sh: split update and post interesting_commits discards 8d1ed2ff0 round-robin-notify.sh: print_mail_recipients discards dfa9c6580 round-robin-notify.sh: Add print_commits discards fd1a7b774 round-robin-notify.sh: Adding --notify parameter discards 22caef4d3 jenkins-helpers.sh: Fix get_baseline_manifest adds 6d8c0b0df jenkins-helpers.sh: Fix get_baseline_manifest
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference 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 (ed9a78ec7) \ N -- N -- N refs/changes/94/44194/3 (6d8c0b0df)
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.
No new revisions were added by this update.
Summary of changes: round-robin-bisect.sh | 633 --------------------------- round-robin-notify.sh | 1152 ------------------------------------------------- 2 files changed, 1785 deletions(-) delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh