This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/93/31093/1 in repository toolchain/jenkins-scripts.
discards d5b710e8d round-robin-bisect.sh: Improve email diagnostics discards 4ecd3dc43 round-robin.sh: Add ${rr[update_baseline]} "rebase" capability adds d20c44a72 round-robin.sh: Add ${rr[update_baseline]} "rebase" capability
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 (d5b710e8d) \ N -- N -- N refs/changes/93/31093/1 (d20c44a72)
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 | 492 -------------------------------------------------- 1 file changed, 492 deletions(-) delete mode 100755 round-robin-bisect.sh