This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/10/29910/2 in repository toolchain/jenkins-scripts.
discards a0698db2d tcwg_kernel-bisect.sh: Simplify linux-next rebase workaround discards 9f60df151 tcwg_kernel-bisect.sh: Simplify checking first_bad's parents discards 3323a9727 tcwg_kernel-bisect.sh: Don't force $reproduce_bisect==true in [...] discards 3fc310049 tcwg-benchmark.sh: Add support for :parallelize parameter in [...] adds a4061179b tcwg-benchmark.sh: Add support for :parallelize parameter in [...]
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 (a0698db2d) \ N -- N -- N refs/changes/10/29910/2 (a4061179b)
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