This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/48/29848/1 in repository toolchain/jenkins-scripts.
discards b0d88f505 tcwg_kernel-bisect.sh: Re-write linux-next workaround as a loop. discards 91096a80b tcwg_kernel-bisect.sh: Re-arrange code in linux-next workaround discards 4f760ce34 tcwg_kernel-bisect.sh: Cleanup handling of $good_rev. discards b8866f36d tcwg_kernel-bisect.sh: Update reproduction instructions discards 10812bcaa tcwg_kernel-bisect.sh: Re-arrange code. discards 10370ddfa tcwg_kernel-bisect.sh: Put bisect test script into artifacts/ discards 582dd8440 tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs discards 883bead54 tcwg_kernel-bisect.sh: Simplify handling of artifact directories discards f484163fb tcwg_kernel-bisect.sh: Remove --confirm_failure option discards c20e3014f round-robin.sh: Improve comment. adds 1efd682eb 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 (b0d88f505) \ N -- N -- N refs/changes/48/29848/1 (1efd682eb)
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 | 360 -------------------------------------------------- 1 file changed, 360 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh