Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/61/41861/4 updated (9fe5761fb -> b69136d2f)

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/61/41861/4 in repository toolchain/jenkins-scripts. discards 9fe5761fb round-robin.sh: Always generate email reports, not just for r [...] adds b69136d2f round-robin.sh: Always generate email reports, not just for r [...] 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 (9fe5761fb) \ N -- N -- N refs/changes/61/41861/4 (b69136d2f) 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/61/41861/3 updated (457e829c9 -> fd844c46a)

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/61/41861/3 in repository toolchain/jenkins-scripts. discards 457e829c9 round-robin.sh: Always generate email reports, not just for r [...] adds fd844c46a round-robin.sh: Always generate email reports, not just for r [...] 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 (457e829c9) \ N -- N -- N refs/changes/61/41861/3 (fd844c46a) 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/61/41861/2 updated (2e6858168 -> 1c87e1302)

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/61/41861/2 in repository toolchain/jenkins-scripts. discards 2e6858168 round-robin.sh: Always generate email reports, not just for r [...] adds 1c87e1302 round-robin.sh: Always generate email reports, not just for r [...] 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 (2e6858168) \ N -- N -- N refs/changes/61/41861/2 (1c87e1302) 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/61/41861/1 updated (85f155f01 -> 6f774b012)

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/61/41861/1 in repository toolchain/jenkins-scripts. discards 85f155f01 round-robin.sh: Always generate email reports, not just for r [...] adds 6f774b012 round-robin.sh: Always generate email reports, not just for r [...] 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 (85f155f01) \ N -- N -- N refs/changes/61/41861/1 (6f774b012) 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/61/41761/1 updated (fc37001f8 -> 04f287d66)

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/61/41761/1 in repository toolchain/jenkins-scripts. discards fc37001f8 MakeRelease.job: Fix expansion of "${check[@]}" adds 04f287d66 MakeRelease.job: Fix expansion of "${check[@]}" 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 (fc37001f8) \ N -- N -- N refs/changes/61/41761/1 (04f287d66) 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/61/39861/1 updated (06588307e -> 0a3c3f974)

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/61/39861/1 in repository toolchain/jenkins-scripts. discards 06588307e jenkins-helpers.sh (convert_args_to_variables): Handle secrets adds 0a3c3f974 jenkins-helpers.sh (convert_args_to_variables): Handle secrets 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 (06588307e) \ N -- N -- N refs/changes/61/39861/1 (0a3c3f974) 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/61/39461/1 updated (2bd9c8da6 -> 561c8feda)

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/61/39461/1 in repository toolchain/jenkins-scripts. discards 2bd9c8da6 tcwg-llvm-release.sh: Set LLVM release compiler to clang > 11 adds 561c8feda tcwg-llvm-release.sh: Set LLVM release compiler to clang > 11 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 (2bd9c8da6) \ N -- N -- N refs/changes/61/39461/1 (561c8feda) 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/61/39361/1 updated (472b7c0be -> b3b487740)

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/61/39361/1 in repository toolchain/jenkins-scripts. discards 472b7c0be print_arch_for_label: Add support for tcwg-armv8_32 and tcwg- [...] adds b3b487740 print_arch_for_label: Add support for tcwg-armv8_32 and tcwg- [...] 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 (472b7c0be) \ N -- N -- N refs/changes/61/39361/1 (b3b487740) 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/61/39261/2 updated (63d3c7451 -> ee5af1d45)

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/61/39261/2 in repository toolchain/jenkins-scripts. discards 63d3c7451 round-robin.sh (clone_repo): Do not use single-branch clones adds ee5af1d45 round-robin.sh (clone_repo): Do not use single-branch clones 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 (63d3c7451) \ N -- N -- N refs/changes/61/39261/2 (ee5af1d45) 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/61/39261/1 updated (971b7dfc1 -> 1361774f0)

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/61/39261/1 in repository toolchain/jenkins-scripts. discards 971b7dfc1 round-robin.sh (clone_repo): Do not use single-branch clones adds 1361774f0 round-robin.sh (clone_repo): Do not use single-branch clones 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 (971b7dfc1) \ N -- N -- N refs/changes/61/39261/1 (1361774f0) 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