This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/26/44226/1 in repository toolchain/jenkins-scripts.
discards 82683c3ce round-robin-bisect.sh: Improve fetching of "bad_git" revision discards 8fe50d5da round-robin-bisect.sh: Cleanup ./bisect/ directory on exit discards c17957aee round-robin-notify.sh: fix for mail of first detection discards 70f4f7f24 round-robin-notify.sh: Fix print_mail_recipients discards 31b3e9239 round-robin-notify.sh: Rework on global flow discards 104000423 tcwg_*-build.sh: remove rr[start_date], as it is now useless adds f314e5045 tcwg_*-build.sh: remove rr[start_date], as it is now useless
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 (82683c3ce) \ N -- N -- N refs/changes/26/44226/1 (f314e5045)
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 | 647 --------------------------- round-robin-notify.sh | 1193 ------------------------------------------------- 2 files changed, 1840 deletions(-) delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh