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

maxim.kuvyrkov pushed a change to reference refs/changes/53/29353/1 in repository toolchain/jenkins-scripts.

discards 88c1ee7cc tcwg_kernel-bisect.sh: Add useful suffixes to artifacts/build [...] discards ba317a795 tcwg_kernel-bisect.sh: Make sure artifacts contain "bad" logs discards 2ac388259 tcwg_kernel-bisect.sh: Tidy up artifacts discards 3cb94b357 tcwg_kernel-bisect.sh: Move email body here from tcwg_kernel.yaml discards a5c2d2aa0 tcwg_kernel-bisect.sh: Send emails only on successful bisects. discards 148291018 tcwg-update-llvmbot-containers.sh: New job script adds ce794b80b tcwg-update-llvmbot-containers.sh: New job script

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 (88c1ee7cc) \ N -- N -- N refs/changes/53/29353/1 (ce794b80b)

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