This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/68/44368/2 in repository toolchain/jenkins-scripts.
discards 1bf9e6781 round-robin-notify.sh: Make mail subject and first line consistent discards fdcc598e4 round-robin.sh (build_abe): Do not build fortran for bare-met [...] adds 4f7964b98 round-robin.sh (build_abe): Do not build fortran for bare-met [...]
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 (1bf9e6781) \ N -- N -- N refs/changes/68/44368/2 (4f7964b98)
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: round-robin-bisect.sh | 647 -------------------------- round-robin-notify.sh | 1237 ------------------------------------------------- 2 files changed, 1884 deletions(-) delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh