This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/24/29724/2 in repository toolchain/jenkins-scripts.
discards d8544fe9d tcwg_kernel-bisect.sh: Handle git-bisect's smartness. discards 60d138622 tcwg_kernel-bisect.sh: Add support to reproduce bisects. discards 1f4200537 tcwg_kernel-bisect.sh: Try harder to bisect linux-next failures discards 46c2519e1 tcwg_kernel-bisect.sh: Cleanup. discards fa931307a tcwg_kernel-bisect.sh: Send emails with useful info when bise [...] discards f238c3d99 tcwg_kernel-build.sh: Make sure manifest declares variables i [...] adds de5d2bdf3 tcwg_kernel-build.sh: Make sure manifest declares variables i [...]
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 (d8544fe9d) \ N -- N -- N refs/changes/24/29724/2 (de5d2bdf3)
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 | 365 -------------------------------------------------- 1 file changed, 365 deletions(-) delete mode 100755 tcwg_kernel-bisect.sh