Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/60/47260/7 updated (f466be443 -> 9599c9813)

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/60/47260/7 in repository toolchain/jenkins-scripts. discards f466be443 tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] adds 9599c9813 tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] 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 (f466be443) \ N -- N -- N refs/changes/60/47260/7 (9599c9813) 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/60/47260/6 updated (96ff76fe9 -> 2e6657120)

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/60/47260/6 in repository toolchain/jenkins-scripts. discards 96ff76fe9 tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] new 2e6657120 tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] 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 (96ff76fe9) \ N -- N -- N refs/changes/60/47260/6 (2e6657120) 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/60/47260/5 updated (35c362b0a -> 52af0b87c)

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/60/47260/5 in repository toolchain/jenkins-scripts. discards 35c362b0a tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] new 52af0b87c tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] 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 (35c362b0a) \ N -- N -- N refs/changes/60/47260/5 (52af0b87c) 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/60/47260/4 updated (15955c3ef -> 62f222f91)

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/60/47260/4 in repository toolchain/jenkins-scripts. discards 15955c3ef tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] new 62f222f91 tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] 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 (15955c3ef) \ N -- N -- N refs/changes/60/47260/4 (62f222f91) 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/60/47260/3 updated (71b933c57 -> 10ebd3597)

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/60/47260/3 in repository toolchain/jenkins-scripts. discards 71b933c57 tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] new 10ebd3597 tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] 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 (71b933c57) \ N -- N -- N refs/changes/60/47260/3 (10ebd3597) 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/60/47260/2 updated (50d25f2c4 -> f5fa93ded)

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/60/47260/2 in repository toolchain/jenkins-scripts. discards 50d25f2c4 tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] new f5fa93ded tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] 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 (50d25f2c4) \ N -- N -- N refs/changes/60/47260/2 (f5fa93ded) 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/60/47260/1 updated (8861919ca -> fe011e217)

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/60/47260/1 in repository toolchain/jenkins-scripts. discards 8861919ca tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] new fe011e217 tcwg_chromium-build.sh,round-robin.sh,jenkins-helpers.sh: Use [...] 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 (8861919ca) \ N -- N -- N refs/changes/60/47260/1 (fe011e217) 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/60/47060/1 updated (45385d075 -> ec5e03034)

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/60/47060/1 in repository toolchain/jenkins-scripts. discards 45385d075 tcwg-update-lnt-results.sh: Ignore tcwg_gnu build-only config [...] adds ec5e03034 tcwg-update-lnt-results.sh: Ignore tcwg_gnu build-only config [...] 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 (45385d075) \ N -- N -- N refs/changes/60/47060/1 (ec5e03034) 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/60/46760/1 updated (0b5823d34 -> 0638b8fe8)

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/60/46760/1 in repository toolchain/jenkins-scripts. discards 0b5823d34 start-container-docker.sh: Fix assert adds 0638b8fe8 start-container-docker.sh: Fix assert 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 (0b5823d34) \ N -- N -- N refs/changes/60/46760/1 (0638b8fe8) 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/60/46660/1 updated (f55630449 -> a30b2b473)

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/60/46660/1 in repository toolchain/jenkins-scripts. discards f55630449 Revert "tcwg_aosp-build.sh: enable libunwind build" adds a30b2b473 Revert "tcwg_aosp-build.sh: enable libunwind build" 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 (f55630449) \ N -- N -- N refs/changes/60/46660/1 (a30b2b473) 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