Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/59/33559/3 updated (32aea9fcd -> 0fdc609bd)

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/59/33559/3 in repository toolchain/jenkins-scripts. discards 32aea9fcd round-robin.sh: Create branch in interesting-commits for cust [...] adds 0fdc609bd round-robin.sh: Create branch in interesting-commits for cust [...] 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 (32aea9fcd) \ N -- N -- N refs/changes/59/33559/3 (0fdc609bd) 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/59/33559/2 updated (3d9f87e3c -> 146525857)

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/59/33559/2 in repository toolchain/jenkins-scripts. discards 3d9f87e3c round-robin.sh: Create branch in interesting-commits for cust [...] adds 146525857 round-robin.sh: Create branch in interesting-commits for cust [...] 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 (3d9f87e3c) \ N -- N -- N refs/changes/59/33559/2 (146525857) 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/59/33559/1 updated (c1bc77381 -> 7f546547d)

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/59/33559/1 in repository toolchain/jenkins-scripts. discards c1bc77381 round-robin.sh: Create branch in interesting-commits for cust [...] new 7f546547d round-robin.sh: Create branch in interesting-commits for cust [...] 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 (c1bc77381) \ N -- N -- N refs/changes/59/33559/1 (7f546547d) 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/59/31859/2 updated (22716e2c3 -> 496cf959b)

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/59/31859/2 in repository toolchain/jenkins-scripts. discards 22716e2c3 tcwg-update-llvmbot-containers.sh: Rework after adding jenkins job adds 496cf959b tcwg-update-llvmbot-containers.sh: Rework after adding jenkins job 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 (22716e2c3) \ N -- N -- N refs/changes/59/31859/2 (496cf959b) 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/59/31859/1 updated (fef502f24 -> 64b704858)

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/59/31859/1 in repository toolchain/jenkins-scripts. discards fef502f24 tcwg-update-llvmbot-containers.sh: Rework after adding jenkins job new 64b704858 tcwg-update-llvmbot-containers.sh: Rework after adding jenkins job 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 (fef502f24) \ N -- N -- N refs/changes/59/31859/1 (64b704858) 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/59/30859/1 updated (ff044c8ba -> 7b9147dac)

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/59/30859/1 in repository toolchain/jenkins-scripts. discards ff044c8ba jenkins-helpers.sh: Don't touch step's artifacts directory un [...] adds 7b9147dac jenkins-helpers.sh: Don't touch step's artifacts directory un [...] 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 (ff044c8ba) \ N -- N -- N refs/changes/59/30859/1 (7b9147dac) 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/59/30459/1 updated (d4758327b -> be232b967)

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/59/30459/1 in repository toolchain/jenkins-scripts. discards d4758327b tcwg_bmk-build.sh: Use "@build_num@" marker instead of "<build_num>" adds be232b967 tcwg_bmk-build.sh: Use "@build_num@" marker instead of "<build_num>" 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 (d4758327b) \ N -- N -- N refs/changes/59/30459/1 (be232b967) 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/59/30359/1 updated (76e0bb578 -> 912747a77)

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/59/30359/1 in repository toolchain/jenkins-scripts. discards 76e0bb578 round-robin.sh: Fix rsync in update_baseline. adds 912747a77 round-robin.sh: Fix rsync in update_baseline. 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 (76e0bb578) \ N -- N -- N refs/changes/59/30359/1 (912747a77) 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/59/30259/3 updated (b535f3acc -> 88f711d63)

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/59/30259/3 in repository toolchain/jenkins-scripts. discards b535f3acc [rr-many 2/N] Update and simplify round-robin.sh: clone_repo() adds 88f711d63 [rr-many 2/N] Update and simplify round-robin.sh: clone_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 (b535f3acc) \ N -- N -- N refs/changes/59/30259/3 (88f711d63) 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/59/30259/2 updated (cf4322655 -> 2f27585ba)

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/59/30259/2 in repository toolchain/jenkins-scripts. discards cf4322655 [rr-many 2/N] Update and simplify round-robin.sh: clone_repo() adds 2f27585ba [rr-many 2/N] Update and simplify round-robin.sh: clone_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 (cf4322655) \ N -- N -- N refs/changes/59/30259/2 (2f27585ba) 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