This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/47/29847/4 in repository toolchain/jenkins-scripts.
discards de4067753 tcwg_kernel-bisect.sh: Re-arrange code in linux-next workaround discards 4d14e7df1 tcwg_kernel-bisect.sh: Cleanup handling of $good_rev. discards 5df7279a1 tcwg_kernel-bisect.sh: Update reproduction instructions discards f08731e2a tcwg_kernel-bisect.sh: Re-arrange code. discards 0b630c5a8 tcwg_kernel-bisect.sh: Put bisect test script into artifacts/ discards dd49fbf78 tcwg_kernel-bisect.sh: Fix manifest handling in reproducer runs discards 06f786a9a tcwg_kernel-bisect.sh: Simplify handling of artifact directories discards 73d563e61 tcwg_kernel-bisect.sh: Remove --confirm_failure option discards 22b7df0e9 round-robin.sh: Improve comment. adds 5ece393b1 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 (de4067753) \ N -- N -- N refs/changes/47/29847/4 (5ece393b1)
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