This is an automated email from the git hooks/post-receive script.
"Maxim Kuvyrkov pushed a change to branch stm32 in repository toolchain/jenkins-scripts.
discards 5cf15311 tcwg-benchmark.sh: Improve verbosity handling discards c644f504 tcwg_bmk-build.sh: Cleanup discards 45932383 tcwg-benchmark.sh: Swap toolchain preparation and board preparation discards bfdad5c9 tcwg-benchmark.sh: Add bits from tcwg-benchmark-bare.sh new 4fcf3d52 tcwg-benchmark.sh: Add bits from tcwg-benchmark-bare.sh new 6919908e tcwg-benchmark.sh: Swap toolchain preparation and board preparation new eaf70353 tcwg_bmk-build.sh: Cleanup new 1c073ed3 tcwg-benchmark.sh: Improve verbosity handling
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch 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 (5cf15311) \ N -- N -- N refs/heads/stm32 (1c073ed3)
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 4 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: tcwg-benchmark.sh | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-)