This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/54/45254/3
in repository toolchain/jenkins-scripts.
discards d00b4ce64 start-container-docker.sh: Rework cleanup of several containers
adds 563702693 start-container-docker.sh: Rework cleanup of several containers
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 (d00b4ce64)
\
N -- N -- N refs/changes/54/45254/3 (563702693)
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/54/45254/2
in repository toolchain/jenkins-scripts.
discards 6ed99509b start-container-docker.sh: Rework cleanup of several containers
adds 79cd32afc start-container-docker.sh: Rework cleanup of several containers
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 (6ed99509b)
\
N -- N -- N refs/changes/54/45254/2 (79cd32afc)
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/54/45254/1
in repository toolchain/jenkins-scripts.
discards 0e0922f07 start-container-docker.sh: Rework cleanup of several containers
adds 32f6f2c0f start-container-docker.sh: Rework cleanup of several containers
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 (0e0922f07)
\
N -- N -- N refs/changes/54/45254/1 (32f6f2c0f)
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/54/45154/4
in repository toolchain/jenkins-scripts.
discards 2146d498c tcwg_gnu-build.sh: Make -mfloat-abi more explicit, use -mtune
adds f74284c9f tcwg_gnu-build.sh: Make -mfloat-abi more explicit, use -mtune
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 (2146d498c)
\
N -- N -- N refs/changes/54/45154/4 (f74284c9f)
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/54/45154/3
in repository toolchain/jenkins-scripts.
discards 1ae3f292c tcwg_gnu-build.sh: Make -mfloat-abi more explicit, use -mtune
adds e4b9b0fe5 tcwg_gnu-build.sh: Make -mfloat-abi more explicit, use -mtune
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 (1ae3f292c)
\
N -- N -- N refs/changes/54/45154/3 (e4b9b0fe5)
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/54/45154/2
in repository toolchain/jenkins-scripts.
discards 51ddd7ab1 tcwg_gnu-build.sh: Make -mfloat-abi more explicit, use -mtune
adds f4e5ad343 tcwg_gnu-build.sh: Make -mfloat-abi more explicit, use -mtune
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 (51ddd7ab1)
\
N -- N -- N refs/changes/54/45154/2 (f4e5ad343)
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/54/45154/1
in repository toolchain/jenkins-scripts.
discards 97056ff0e tcwg_gnu-build.sh: Make -mfloat-abi more explicit, use -mtune
new a718fe880 tcwg_gnu-build.sh: Make -mfloat-abi more explicit, use -mtune
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 (97056ff0e)
\
N -- N -- N refs/changes/54/45154/1 (a718fe880)
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/54/45054/1
in repository toolchain/jenkins-scripts.
discards 813f7853d pw-*.sh: Remove support for {appl,test}-{fail,pass} bundles
adds aaefb0555 pw-*.sh: Remove support for {appl,test}-{fail,pass} bundles
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 (813f7853d)
\
N -- N -- N refs/changes/54/45054/1 (aaefb0555)
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/54/44854/9
in repository toolchain/jenkins-scripts.
discards a97274116 round-robin.sh: Start bisection from top of branch, rather th [...]
new fc71c0ae0 round-robin.sh: Start bisection from top of branch, rather th [...]
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 (a97274116)
\
N -- N -- N refs/changes/54/44854/9 (fc71c0ae0)
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/54/44854/8
in repository toolchain/jenkins-scripts.
discards 42b4986c5 round-robin.sh: Start bisection from top of branch, rather th [...]
new ba04794e9 round-robin.sh: Start bisection from top of branch, rather th [...]
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 (42b4986c5)
\
N -- N -- N refs/changes/54/44854/8 (ba04794e9)
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.