Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/94/32994/9 updated (b7ee25a42 -> c074c8400)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/94/32994/9 in repository toolchain/jenkins-scripts. discards b7ee25a42 jenkins-helpers.sh: Handle paths in run_step's arguments adds c074c8400 jenkins-helpers.sh: Handle paths in run_step's arguments 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 (b7ee25a42) \ N -- N -- N refs/changes/94/32994/9 (c074c8400) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/94/32994/8 updated (212e47057 -> d9ebdde61)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/94/32994/8 in repository toolchain/jenkins-scripts. discards 212e47057 jenkins-helpers.sh: Handle paths in run_step's arguments new d9ebdde61 jenkins-helpers.sh: Handle paths in run_step's arguments 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 (212e47057) \ N -- N -- N refs/changes/94/32994/8 (d9ebdde61) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/94/32994/7 updated (cc6516a21 -> 8b972be3d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/94/32994/7 in repository toolchain/jenkins-scripts. discards cc6516a21 jenkins-helpers.sh: Handle paths in run_step's arguments new 8b972be3d jenkins-helpers.sh: Handle paths in run_step's arguments 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 (cc6516a21) \ N -- N -- N refs/changes/94/32994/7 (8b972be3d) 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.

1 year, 3 months

[gcc] branch master updated (d2fc64c8578 -> 8c71830b51e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from d2fc64c8578 c++: Mostly concepts related formatting fixes new 8c71830b51e c++: parse error with -std=c++14 -fconcepts [PR116071] 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/parser.cc | 10 +++++++--- gcc/testsuite/g++.dg/parse/pr116071.C | 18 ++++++++++++++++++ 2 files changed, 25 insertions(+), 3 deletions(-) create mode 100644 gcc/testsuite/g++.dg/parse/pr116071.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/94/32994/6 updated (e52415cf9 -> 5a56f199f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/94/32994/6 in repository toolchain/jenkins-scripts. discards e52415cf9 jenkins-helpers.sh: Handle paths in run_step's arguments new 5a56f199f jenkins-helpers.sh: Handle paths in run_step's arguments 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 (e52415cf9) \ N -- N -- N refs/changes/94/32994/6 (5a56f199f) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/94/32994/5 updated (ce7c700ab -> 1ff4f1962)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/94/32994/5 in repository toolchain/jenkins-scripts. discards ce7c700ab jenkins-helpers.sh: Handle paths in run_step's arguments new 1ff4f1962 jenkins-helpers.sh: Handle paths in run_step's arguments 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 (ce7c700ab) \ N -- N -- N refs/changes/94/32994/5 (1ff4f1962) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/94/32994/4 updated (4b3041768 -> 9c6dc5418)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/94/32994/4 in repository toolchain/jenkins-scripts. discards 4b3041768 jenkins-helpers.sh: Handle paths in run_step's arguments new 9c6dc5418 jenkins-helpers.sh: Handle paths in run_step's arguments 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 (4b3041768) \ N -- N -- N refs/changes/94/32994/4 (9c6dc5418) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/94/32994/3 updated (99d715e2b -> 7e993bb03)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/94/32994/3 in repository toolchain/jenkins-scripts. discards 99d715e2b jenkins-helpers.sh: Handle paths in run_step's arguments adds 7e993bb03 jenkins-helpers.sh: Handle paths in run_step's arguments 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 (99d715e2b) \ N -- N -- N refs/changes/94/32994/3 (7e993bb03) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/94/32994/2 updated (0a04801d1 -> 7a4cafa24)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/94/32994/2 in repository toolchain/jenkins-scripts. discards 0a04801d1 jenkins-helpers.sh: Handle paths in run_step's arguments adds 7a4cafa24 jenkins-helpers.sh: Handle paths in run_step's arguments 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 (0a04801d1) \ N -- N -- N refs/changes/94/32994/2 (7a4cafa24) 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.

1 year, 3 months

[toolchain/jenkins-scripts] reference refs/changes/94/32994/1 updated (2f262d191 -> a4bb65e78)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/94/32994/1 in repository toolchain/jenkins-scripts. discards 2f262d191 jenkins-helpers.sh: Handle paths in run_step's arguments adds a4bb65e78 jenkins-helpers.sh: Handle paths in run_step's arguments 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 (2f262d191) \ N -- N -- N refs/changes/94/32994/1 (a4bb65e78) 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.

1 year, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024