This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/31/45731/16
in repository toolchain/jenkins-scripts.
discards 45dfd2f50 tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
adds 418d7bb71 tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
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 (45dfd2f50)
\
N -- N -- N refs/changes/31/45731/16 (418d7bb71)
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/31/45731/15
in repository toolchain/jenkins-scripts.
discards 5f8da4765 tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
adds 452b3a905 tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
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 (5f8da4765)
\
N -- N -- N refs/changes/31/45731/15 (452b3a905)
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/31/45731/14
in repository toolchain/jenkins-scripts.
discards 88a10ab3c tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
new 0f8a03183 tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
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 (88a10ab3c)
\
N -- N -- N refs/changes/31/45731/14 (0f8a03183)
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/31/45731/13
in repository toolchain/jenkins-scripts.
discards 8fd268a9d tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
new b00297d93 tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
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 (8fd268a9d)
\
N -- N -- N refs/changes/31/45731/13 (b00297d93)
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/31/45731/12
in repository toolchain/jenkins-scripts.
discards 7a42567b5 tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
new 43108a446 tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
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 (7a42567b5)
\
N -- N -- N refs/changes/31/45731/12 (43108a446)
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/31/45731/11
in repository toolchain/jenkins-scripts.
discards 2c26f5da4 tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
new 3fb164671 tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
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 (2c26f5da4)
\
N -- N -- N refs/changes/31/45731/11 (3fb164671)
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/31/45731/10
in repository toolchain/jenkins-scripts.
discards ecdd0229e tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
new 6298e9203 tcwg_gnu-config.sh (settings_for_ci_project_and_config): add [...]
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 (ecdd0229e)
\
N -- N -- N refs/changes/31/45731/10 (6298e9203)
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/31/45731/1
in repository toolchain/jenkins-scripts.
discards c8fc06034 jenkins-helpers.sh (settings_for_ci_project_and_target): add [...]
new dfcb7898d jenkins-helpers.sh (settings_for_ci_project_and_target): add [...]
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 (c8fc06034)
\
N -- N -- N refs/changes/31/45731/1 (dfcb7898d)
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/31/45431/1
in repository toolchain/jenkins-scripts.
discards e4dddb69d tcwg_gnu-build.sh: Add --disable-timeoutfactor option to chec [...]
new acc2e9802 tcwg_gnu-build.sh: Add --disable-timeoutfactor option to chec [...]
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 (e4dddb69d)
\
N -- N -- N refs/changes/31/45431/1 (acc2e9802)
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/31/44931/1
in repository toolchain/jenkins-scripts.
discards 50ffd5cac tcwg_bmk-build.sh: Fix perf record directory
adds 8969fd1ff tcwg_bmk-build.sh: Fix perf record directory
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 (50ffd5cac)
\
N -- N -- N refs/changes/31/44931/1 (8969fd1ff)
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.