This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/07/37407/2 in repository toolchain/jenkins-scripts.
discards e3dff5bb4 round-robin-bisect.sh: Remove obsolete marker discards 8b78dcbbb round-robin-bisect.sh: Generalize logic of handling "reset" commit discards 499beadee round-robin-bisect.sh: Make handling of unsuccessful bisects [...] discards 36aa35cac round-robin-bisect.sh: Make code to trigger follow-up builds [...] discards d04c755cb round-robin-bisect.sh: Make logic of handling successful bise [...] discards 8bdc7c170 round-robin-bisect.sh: Simplify filtering of interesting commits discards a9ee3b7ff tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE adds e1b7cb695 tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
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 (e3dff5bb4) \ N -- N -- N refs/changes/07/37407/2 (e1b7cb695)
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 | 719 -------------------------------------------------- 1 file changed, 719 deletions(-) delete mode 100755 round-robin-bisect.sh