This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/63/47163/1
in repository toolchain/jenkins-scripts.
discards 03501f7d3 tcwg_chromium-config.sh: deps sha1s for fast demo mode
new 943100b58 tcwg_chromium-config.sh: deps sha1s for fast demo mode
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 (03501f7d3)
\
N -- N -- N refs/changes/63/47163/1 (943100b58)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/63/46963/4
in repository toolchain/jenkins-scripts.
discards 41dadf8b9 round-robin-notify.sh (generate_lnt_report): Add statistics
adds a5ecd00c4 round-robin-notify.sh (generate_lnt_report): Add statistics
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 (41dadf8b9)
\
N -- N -- N refs/changes/63/46963/4 (a5ecd00c4)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/63/46963/3
in repository toolchain/jenkins-scripts.
discards 2d8b671e9 round-robin-notify.sh (generate_lnt_report): Add statistics
new 0ad677da9 round-robin-notify.sh (generate_lnt_report): Add statistics
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 (2d8b671e9)
\
N -- N -- N refs/changes/63/46963/3 (0ad677da9)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/63/46963/2
in repository toolchain/jenkins-scripts.
discards 199855688 round-robin-notify.sh (generate_lnt_report): Add statistics
new 7fb21c0ae round-robin-notify.sh (generate_lnt_report): Add statistics
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 (199855688)
\
N -- N -- N refs/changes/63/46963/2 (7fb21c0ae)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/63/46963/1
in repository toolchain/jenkins-scripts.
discards 84047dd95 round-robin-notify.sh (generate_lnt_report): Add statistics
new 1f3b6b9ba round-robin-notify.sh (generate_lnt_report): Add statistics
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 (84047dd95)
\
N -- N -- N refs/changes/63/46963/1 (1f3b6b9ba)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/63/46763/1
in repository toolchain/jenkins-scripts.
discards ae8055a90 tcwg_gnu-build.sh: Fix typo
adds 949d6502a tcwg_gnu-build.sh: Fix typo
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 (ae8055a90)
\
N -- N -- N refs/changes/63/46763/1 (949d6502a)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/63/46563/1
in repository toolchain/jenkins-scripts.
discards 170ec1124 precommit-test.sh: Use better "grep" parameters
adds fa6895d0a precommit-test.sh: Use better "grep" parameters
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 (170ec1124)
\
N -- N -- N refs/changes/63/46563/1 (fa6895d0a)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/63/45763/2
in repository toolchain/jenkins-scripts.
discards 24d9ebd2c Rewrite history for VECT and SVE configs.
adds 20a78b157 Rewrite history for VECT and SVE configs.
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 (24d9ebd2c)
\
N -- N -- N refs/changes/63/45763/2 (20a78b157)
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:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/63/45763/1
in repository toolchain/jenkins-scripts.
discards 8f16a5516 Rewrite history for VECT and SVE configs.
new f96bcb3ae Rewrite history for VECT and SVE configs.
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 (8f16a5516)
\
N -- N -- N refs/changes/63/45763/1 (f96bcb3ae)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/63/45663/1
in repository toolchain/jenkins-scripts.
discards 93d2f6424 round-robin-notify.sh (print_mail_recipients): Remove tcwg-bu [...]
discards c094ee421 round-robin-notify.sh (print_mail_recipients): Fix bug
discards 8d5a975a1 round-robin-notify.sh (print_mail_recipients): Better handle [...]
discards 7a14888fc round-robin-notify.sh (print_last_icommit): Indent and fix re [...]
discards 22471f428 round-robin-notify.sh (print_mail_recipients): Enable email n [...]
discards 3d9a6a027 round-robin-notify.sh (print_mail_recipients): Make more flexible
discards 291741672 round-robin-notify.sh (print_mail_recipients): Simplify
discards addf3b386 round-robin-notify.sh: Re-enable emails to clang-built-linux project
discards 41f2ed493 round-robin-notify.sh (update_interesting_commits): Cleanup u [...]
discards 80d12e5ff round-robin-notify.sh (update_interesting_commits): Rename su [...]
discards 7eacfd71e round-robin-notify.sh (update_interesting_commits): Add detai [...]
discards 11c2ca8e2 tcwg_bmk-build.sh: rename samples-variabilty.py script
adds 9485a171d tcwg_bmk-build.sh: rename samples-variabilty.py 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 (93d2f6424)
\
N -- N -- N refs/changes/63/45663/1 (9485a171d)
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-baseline.sh | 455 ------------
round-robin-bisect.sh | 655 ------------------
round-robin-notify.sh | 1754 -----------------------------------------------
3 files changed, 2864 deletions(-)
delete mode 100755 round-robin-baseline.sh
delete mode 100755 round-robin-bisect.sh
delete mode 100755 round-robin-notify.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.