This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/92/32992/9
in repository toolchain/jenkins-scripts.
discards e90070b6b tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
adds 14dcbdff9 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
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 (e90070b6b)
\
N -- N -- N refs/changes/92/32992/9 (14dcbdff9)
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/92/32992/8
in repository toolchain/jenkins-scripts.
discards 07013a283 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
adds 8b405189c tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
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 (07013a283)
\
N -- N -- N refs/changes/92/32992/8 (8b405189c)
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/92/32992/7
in repository toolchain/jenkins-scripts.
discards 2bc558297 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
adds e32578190 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
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 (2bc558297)
\
N -- N -- N refs/changes/92/32992/7 (e32578190)
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/92/32992/6
in repository toolchain/jenkins-scripts.
discards 680f211e6 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
adds 9bf4cd51c tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
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 (680f211e6)
\
N -- N -- N refs/changes/92/32992/6 (9bf4cd51c)
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/92/32992/5
in repository toolchain/jenkins-scripts.
discards c8c1df641 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
adds afe7deb73 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
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 (c8c1df641)
\
N -- N -- N refs/changes/92/32992/5 (afe7deb73)
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/92/32992/4
in repository toolchain/jenkins-scripts.
discards fc210f876 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
adds 7f7ed45cb tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
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 (fc210f876)
\
N -- N -- N refs/changes/92/32992/4 (7f7ed45cb)
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/92/32992/3
in repository toolchain/jenkins-scripts.
discards 87f0e8be4 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
adds 0c3bb5623 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
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 (87f0e8be4)
\
N -- N -- N refs/changes/92/32992/3 (0c3bb5623)
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/92/32992/2
in repository toolchain/jenkins-scripts.
discards f96502978 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
new 59961966e tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
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 (f96502978)
\
N -- N -- N refs/changes/92/32992/2 (59961966e)
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/92/32992/11
in repository toolchain/jenkins-scripts.
discards bc1af4540 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
adds 3121293e4 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
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 (bc1af4540)
\
N -- N -- N refs/changes/92/32992/11 (3121293e4)
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/92/32992/10
in repository toolchain/jenkins-scripts.
discards 544d856fd tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
adds 430b51147 tcwg_bmk-build.sh: Add support for Opt1-vs-Opt2 configurations
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 (544d856fd)
\
N -- N -- N refs/changes/92/32992/10 (430b51147)
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.