Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/52/30852/2 updated (c98ba8dcf -> 1ecf296e5)

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/52/30852/2 in repository toolchain/jenkins-scripts. discards c98ba8dcf tcwg_bmk-build.sh: Consider only final executable size for re [...] adds 1ecf296e5 tcwg_bmk-build.sh: Consider only final executable size for re [...] 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 (c98ba8dcf) \ N -- N -- N refs/changes/52/30852/2 (1ecf296e5) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/30852/1 updated (f5ac50ab7 -> 45ca45417)

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/52/30852/1 in repository toolchain/jenkins-scripts. discards f5ac50ab7 tcwg_bmk-build.sh: Consider only final executable size for re [...] new 45ca45417 tcwg_bmk-build.sh: Consider only final executable size for re [...] 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 (f5ac50ab7) \ N -- N -- N refs/changes/52/30852/1 (45ca45417) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/30752/6 updated (278e12dee -> 7be332ecf)

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/52/30752/6 in repository toolchain/jenkins-scripts. discards 278e12dee Patch [3/3] Merge tcwg_gnu: Add support for various bootstrap [...] adds 7be332ecf Patch [3/3] Merge tcwg_gnu: Add support for various bootstrap [...] 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 (278e12dee) \ N -- N -- N refs/changes/52/30752/6 (7be332ecf) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/30752/5 updated (a11f31f2b -> 8941e9ef3)

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/52/30752/5 in repository toolchain/jenkins-scripts. discards a11f31f2b Patch [3/3] Merge tcwg_gnu: Add support for various bootstrap [...] new 8941e9ef3 Patch [3/3] Merge tcwg_gnu: Add support for various bootstrap [...] 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 (a11f31f2b) \ N -- N -- N refs/changes/52/30752/5 (8941e9ef3) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/30752/4 updated (51ab53eb7 -> 1c8cd80d5)

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/52/30752/4 in repository toolchain/jenkins-scripts. discards 51ab53eb7 Patch [3/3] Merge tcwg_gnu: Add support for various bootstrap [...] new 1c8cd80d5 Patch [3/3] Merge tcwg_gnu: Add support for various bootstrap [...] 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 (51ab53eb7) \ N -- N -- N refs/changes/52/30752/4 (1c8cd80d5) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/30752/3 updated (2d0e07bfc -> 89d371977)

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/52/30752/3 in repository toolchain/jenkins-scripts. discards 2d0e07bfc Patch [3/3] Merge tcwg_gnu: Add support for various bootstrap [...] new 89d371977 Patch [3/3] Merge tcwg_gnu: Add support for various bootstrap [...] 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 (2d0e07bfc) \ N -- N -- N refs/changes/52/30752/3 (89d371977) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/30752/2 updated (b286189b2 -> e2fe4c187)

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/52/30752/2 in repository toolchain/jenkins-scripts. discards b286189b2 Patch [3/3] Merge tcwg_gnu: Add support for various bootstrap [...] new e2fe4c187 Patch [3/3] Merge tcwg_gnu: Add support for various bootstrap [...] 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 (b286189b2) \ N -- N -- N refs/changes/52/30752/2 (e2fe4c187) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/30752/1 updated (5e972d4dc -> 565a3d70e)

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/52/30752/1 in repository toolchain/jenkins-scripts. discards 5e972d4dc Patch [3/3] Merge tcwg_gnu: Add support for various bootstrap [...] new 565a3d70e Patch [3/3] Merge tcwg_gnu: Add support for various bootstrap [...] 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 (5e972d4dc) \ N -- N -- N refs/changes/52/30752/1 (565a3d70e) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/30352/1 updated (e05d0df70 -> 4739fac14)

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/52/30352/1 in repository toolchain/jenkins-scripts. discards e05d0df70 jenkins-helpers.sh: Remove stale locks in git repos. adds 4739fac14 jenkins-helpers.sh: Remove stale locks in git repos. 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 (e05d0df70) \ N -- N -- N refs/changes/52/30352/1 (4739fac14) 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.

11 months, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/30052/4 updated (f85158eef -> 6e2d29a62)

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/52/30052/4 in repository toolchain/jenkins-scripts. discards f85158eef tcwg-benchmark-results.sh: Rework and cleanup. adds 6e2d29a62 tcwg-benchmark-results.sh: Rework and cleanup. 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 (f85158eef) \ N -- N -- N refs/changes/52/30052/4 (6e2d29a62) 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.

11 months, 4 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024