This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch master
in repository gcc.
from 679086172b8 [rtl-optimization/116037] Explicitly track if a destination [...]
new d2fc64c8578 c++: Mostly concepts related formatting fixes
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:
gcc/cp/constraint.cc | 203 ++++++++++++++++++++++++++-------------------------
gcc/cp/cp-tree.h | 47 ++++++------
gcc/cp/logic.cc | 99 +++++++++++++------------
3 files changed, 175 insertions(+), 174 deletions(-)
--
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/65/29865/3
in repository toolchain/jenkins-scripts.
discards 3269f95e6 tcwg_kernel-build.sh: Fix bisection of GCC regressions
adds 23b43762c tcwg_kernel-build.sh: Fix bisection of GCC regressions
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 (3269f95e6)
\
N -- N -- N refs/changes/65/29865/3 (23b43762c)
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/65/29865/2
in repository toolchain/jenkins-scripts.
discards 6f4fd923b tcwg_kernel-build.sh: Fix bisection of GCC regressions
adds fb25d76f6 tcwg_kernel-build.sh: Fix bisection of GCC regressions
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 (6f4fd923b)
\
N -- N -- N refs/changes/65/29865/2 (fb25d76f6)
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/65/29865/1
in repository toolchain/jenkins-scripts.
discards 84a5c7411 tcwg_kernel-build.sh: Fix bisection of GCC regressions
adds b1421db42 tcwg_kernel-build.sh: Fix bisection of GCC regressions
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 (84a5c7411)
\
N -- N -- N refs/changes/65/29865/1 (b1421db42)
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/65/29765/1
in repository toolchain/jenkins-scripts.
discards 36f13e70c tcwg_kernel-bisect.sh: Create symlinks for moved files
discards 6c5849c4b jenkins-helpers.sh: Implement stack logic for __manifest_file
adds 18ff139a5 jenkins-helpers.sh: Implement stack logic for __manifest_file
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 (36f13e70c)
\
N -- N -- N refs/changes/65/29765/1 (18ff139a5)
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:
tcwg_kernel-bisect.sh | 381 --------------------------------------------------
1 file changed, 381 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
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/65/29065/2
in repository toolchain/jenkins-scripts.
discards ce694db9f jenkins-helpers: Add missing print_kernel_target
adds 1378553ff jenkins-helpers: Add missing print_kernel_target
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 (ce694db9f)
\
N -- N -- N refs/changes/65/29065/2 (1378553ff)
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/65/29065/1
in repository toolchain/jenkins-scripts.
discards 966b2ada9 jenkins-helpers: Add missing print_kernel_target
adds 1a4b00c9d jenkins-helpers: Add missing print_kernel_target
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 (966b2ada9)
\
N -- N -- N refs/changes/65/29065/1 (1a4b00c9d)
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/64/46764/2
in repository toolchain/jenkins-scripts.
discards 849d5be34 start-container-docker.sh: Enable WSL-Interop
adds 442689de5 start-container-docker.sh: Enable WSL-Interop
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 (849d5be34)
\
N -- N -- N refs/changes/64/46764/2 (442689de5)
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/64/46764/1
in repository toolchain/jenkins-scripts.
discards 9e5c62695 start-container-docker.sh: Enable WSL-Interop
new 7cf856e51 start-container-docker.sh: Enable WSL-Interop
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 (9e5c62695)
\
N -- N -- N refs/changes/64/46764/1 (7cf856e51)
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/64/45964/1
in repository toolchain/jenkins-scripts.
discards 42e80f223 generate-cimonitor-dashboard.py: artifact_version is now chec [...]
adds 8d937e289 generate-cimonitor-dashboard.py: artifact_version is now 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 (42e80f223)
\
N -- N -- N refs/changes/64/45964/1 (8d937e289)
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.