This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/94/44194/1 in repository toolchain/jenkins-scripts.
discards 17733a917 round-robin-notify.sh: remove finalize_mail discards b338e55ca round-robin-notify.sh: print_mail_body discards 1f817c66c round-robin-notify.sh: generate jira files directly instead o [...] discards 8f9b0b620 round-robin-notify.sh: Add print_result print_config and use [...] discards 87da6e4e0 round-robin-notify.sh: split update and post interesting_commits discards a13ad33ce round-robin-notify.sh: print_mail_recipients discards 24a3cfec6 round-robin-notify.sh: Add print_commits discards d3105f260 round-robin.sh: Add results_date to manifest.sh new 31ac4c7c3 round-robin.sh: Add results_date to manifest.sh
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 (17733a917) \ N -- N -- N refs/changes/94/44194/1 (31ac4c7c3)
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 1 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: round-robin-bisect.sh | 633 --------------------------- round-robin-notify.sh | 1158 ------------------------------------------------- 2 files changed, 1791 deletions(-) delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh