This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/94/44594/1 in repository toolchain/jenkins-scripts.
discards 566936141 round-robin-notify.sh (print_mail_recipients): Simplify discards eb0f5e727 round-robin-notify.sh: Add "--stage init" parameter discards 3dd848fd8 round-robin-notify.sh: Simplify flow of update_interesting_commits() discards fc568bf52 round-robin-notify.sh: Replace regenerate_regression_details() discards e607eb3e1 round-robin-notify.sh: Add a comment discards 8afcd0137 round-robin-notify.sh: Fixed commit display discards 9e6758923 round-robin-notify.sh: Replace reproduction instruction by a link discards 0c4cf34ea round-robin-notify.sh: Replace full commit by its link discards 67e377147 tcwg-cleanup-stale-workspaces.sh: Make a bit more robust adds 94e78ef96 tcwg-cleanup-stale-workspaces.sh: Make a bit more robust
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 (566936141) \ N -- N -- N refs/changes/94/44594/1 (94e78ef96)
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