This is an automated email from the git hooks/post-receive script.

maxim.kuvyrkov pushed a change to reference refs/changes/47/29847/2 in repository toolchain/jenkins-scripts.

discards 9af7bec1f tcwg_kernel-bisect.sh: Re-arrange code in linux-next workaround discards 391f1ac72 tcwg_kernel-bisect.sh: Cleanup handling of $good_rev. discards c80275f2d tcwg_kernel-bisect.sh: Update reproduction instructions discards 8de2d5a52 tcwg_kernel-bisect.sh: Re-arrange code. discards 96da56ccf tcwg_kernel-bisect.sh: Put bisect test script into artifacts/ discards bdae8b950 tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs discards d772207c8 tcwg_kernel-bisect.sh: Simplify handling of artifact directories discards 82ffe64ac tcwg_kernel-bisect.sh: Remove --confirm_failure option discards bedb5b13e round-robin.sh: Improve comment. adds 964a669f3 round-robin.sh: Improve comment.

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 (9af7bec1f) \ N -- N -- N refs/changes/47/29847/2 (964a669f3)

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: tcwg_kernel-bisect.sh | 362 -------------------------------------------------- 1 file changed, 362 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh