This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/94/44594/2 in repository toolchain/jenkins-scripts.
discards 6f83b4d4f round-robin-notify.sh (print_mail_recipients): Simplify discards 8ea07ea60 round-robin-notify.sh: Add "--stage init" parameter discards 342e8ae91 round-robin-notify.sh: Simplify flow of update_interesting_commits() discards 3f4f1d952 round-robin-notify.sh: Replace regenerate_regression_details() discards 7d29d66ca round-robin-notify.sh: Add a comment discards 5f6b078f6 tcwg-update-llvmbot-containers.sh (tcwg-g3-0*): Update allocation adds 810278793 tcwg-update-llvmbot-containers.sh (tcwg-g3-0*): Update allocation
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 (6f83b4d4f) \ N -- N -- N refs/changes/94/44594/2 (810278793)
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-baseline.sh | 166 ------ round-robin-bisect.sh | 653 ----------------------- round-robin-notify.sh | 1363 ----------------------------------------------- 3 files changed, 2182 deletions(-) delete mode 100755 round-robin-baseline.sh delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh