Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/40/39640/2 updated (c55fbed24 -> 8ba95aef4)

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/40/39640/2 in repository toolchain/jenkins-scripts. discards c55fbed24 tcwg-llvm-release.bat: Fix calculation of package name adds 8ba95aef4 tcwg-llvm-release.bat: Fix calculation of package name 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 (c55fbed24) \ N -- N -- N refs/changes/40/39640/2 (8ba95aef4) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/40/39640/1 updated (40bbfba88 -> ceced545a)

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/40/39640/1 in repository toolchain/jenkins-scripts. discards 40bbfba88 tcwg-llvm-release.bat: Fix calculation of package name new ceced545a tcwg-llvm-release.bat: Fix calculation of package name 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 (40bbfba88) \ N -- N -- N refs/changes/40/39640/1 (ceced545a) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/40/39240/1 updated (38387e546 -> 74c84cc2d)

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/40/39240/1 in repository toolchain/jenkins-scripts. discards 38387e546 round-robin.sh: Simplify logic for cloning baseline repo adds 74c84cc2d round-robin.sh: Simplify logic for cloning baseline repo 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 (38387e546) \ N -- N -- N refs/changes/40/39240/1 (74c84cc2d) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/40/35440/1 updated (a367dd26b -> 0692a0fbb)

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/40/35440/1 in repository toolchain/jenkins-scripts. discards a367dd26b round-robin-bisect.sh: Fix references to $linux_url discards c0e26f302 round-robin-bisect.sh: Fix shellcheck warnings discards f83ab343d round-robin*.sh: Pass component URL alongside component branches adds 0692a0fbb round-robin*.sh: Pass component URL alongside component branches 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 (a367dd26b) \ N -- N -- N refs/changes/40/35440/1 (0692a0fbb) 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: round-robin-bisect.sh | 651 -------------------------------------------------- 1 file changed, 651 deletions(-) delete mode 100755 round-robin-bisect.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/40/35040/2 updated (95dad9a20 -> 2a4756eb8)

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/40/35040/2 in repository toolchain/jenkins-scripts. discards 95dad9a20 jenkins-helpers.sh: Fix print_node_with_least_containers adds 2a4756eb8 jenkins-helpers.sh: Fix print_node_with_least_containers 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 (95dad9a20) \ N -- N -- N refs/changes/40/35040/2 (2a4756eb8) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/40/35040/1 updated (594c73c63 -> f1ae5581a)

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/40/35040/1 in repository toolchain/jenkins-scripts. discards 594c73c63 jenkins-helpers.sh: Fix print_node_with_least_containers new f1ae5581a jenkins-helpers.sh: Fix print_node_with_least_containers 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 (594c73c63) \ N -- N -- N refs/changes/40/35040/1 (f1ae5581a) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/40/34740/4 updated (9870685df -> 0a1c849f4)

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/40/34740/4 in repository toolchain/jenkins-scripts. discards 9870685df sanity-check.sh: Allow local users to check individual scripts adds 0a1c849f4 sanity-check.sh: Allow local users to check individual scripts 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 (9870685df) \ N -- N -- N refs/changes/40/34740/4 (0a1c849f4) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/40/34740/3 updated (a85ebcfbb -> 47d5f6c91)

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/40/34740/3 in repository toolchain/jenkins-scripts. discards a85ebcfbb sanity-check.sh: Allow local users to check individual scripts new 47d5f6c91 sanity-check.sh: Allow local users to check individual scripts 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 (a85ebcfbb) \ N -- N -- N refs/changes/40/34740/3 (47d5f6c91) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/40/34740/2 updated (8c25f16c9 -> 0a077a5f1)

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/40/34740/2 in repository toolchain/jenkins-scripts. discards 8c25f16c9 sanity-check.sh: Allow local users to check individual scripts new 0a077a5f1 sanity-check.sh: Allow local users to check individual scripts 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 (8c25f16c9) \ N -- N -- N refs/changes/40/34740/2 (0a077a5f1) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/40/34740/1 updated (c1281e094 -> 624d8f488)

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/40/34740/1 in repository toolchain/jenkins-scripts. discards c1281e094 sanity-check.sh: Allow local users to check individual scripts new 624d8f488 sanity-check.sh: Allow local users to check individual scripts 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 (c1281e094) \ N -- N -- N refs/changes/40/34740/1 (624d8f488) 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, 3 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024