This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/70/38070/3
in repository toolchain/jenkins-scripts.
discards 32d746885 Make build_abe apply an optional patch specified in $2 to $co [...]
new aabe89640 Make build_abe apply an optional patch specified in $2 to $co [...]
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 (32d746885)
\
N -- N -- N refs/changes/70/38070/3 (aabe89640)
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/70/38070/2
in repository toolchain/jenkins-scripts.
discards 3fd7c46b6 Make build_abe apply an optional patch specified in $2 to $co [...]
new fd0a3e4ec Make build_abe apply an optional patch specified in $2 to $co [...]
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 (3fd7c46b6)
\
N -- N -- N refs/changes/70/38070/2 (fd0a3e4ec)
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/70/38070/1
in repository toolchain/jenkins-scripts.
discards 54f525720 Apply and revert metric patches to stage-2 gcc.
new de477839a Apply and revert metric patches to stage-2 gcc.
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 (54f525720)
\
N -- N -- N refs/changes/70/38070/1 (de477839a)
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/70/30770/1
in repository toolchain/jenkins-scripts.
discards f70292585 round-robin.sh: Fix un-intutive bash behavior
adds f99bc369c round-robin.sh: Fix un-intutive bash behavior
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 (f70292585)
\
N -- N -- N refs/changes/70/30770/1 (f99bc369c)
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/70/30470/1
in repository toolchain/jenkins-scripts.
discards 41b06db09 tcwg_bmk-build.sh: Handle -Oz configurations
adds a5e9060dc tcwg_bmk-build.sh: Handle -Oz 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 (41b06db09)
\
N -- N -- N refs/changes/70/30470/1 (a5e9060dc)
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/70/30270/1
in repository toolchain/jenkins-scripts.
discards 881670f4c Revert "[tcwg_gnu] Merge branch 'master' into tcwg_gnu"
new aeaabd3e9 Revert "[tcwg_gnu] Merge branch 'master' into tcwg_gnu"
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 (881670f4c)
\
N -- N -- N refs/changes/70/30270/1 (aeaabd3e9)
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/70/29570/3
in repository toolchain/jenkins-scripts.
discards 608c5dff2 tcwg-benchmark.sh: Force use of build_container_port when cop [...]
adds 6edaaff11 tcwg-benchmark.sh: Force use of build_container_port when cop [...]
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 (608c5dff2)
\
N -- N -- N refs/changes/70/29570/3 (6edaaff11)
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/70/29570/2
in repository toolchain/jenkins-scripts.
discards 08886f5ee tcwg-benchmark.sh: Force use of build_container_port when cop [...]
adds d14897d81 tcwg-benchmark.sh: Force use of build_container_port when cop [...]
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 (08886f5ee)
\
N -- N -- N refs/changes/70/29570/2 (d14897d81)
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/70/29570/1
in repository toolchain/jenkins-scripts.
discards b1a022f79 tcwg-benchmark.sh: Force use of build_container_port when cop [...]
adds 73f6e35c8 tcwg-benchmark.sh: Force use of build_container_port when cop [...]
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 (b1a022f79)
\
N -- N -- N refs/changes/70/29570/1 (73f6e35c8)
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/70/29270/1
in repository toolchain/jenkins-scripts.
discards bdbf886eb tcwg-update-host-containers.sh, tcwg-start-container.sh: Refa [...]
adds f3c63fe41 tcwg-update-host-containers.sh, tcwg-start-container.sh: Refa [...]
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 (bdbf886eb)
\
N -- N -- N refs/changes/70/29270/1 (f3c63fe41)
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.