Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/91/44491/1 updated (cbdfc4484 -> 2be6134fd)

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/91/44491/1 in repository toolchain/jenkins-scripts. discards cbdfc4484 round-robin-notify.sh: Remove unnecessary info from jira reports discards b4ae8bb85 round-robin-notify.sh: Simplify single_commit_p() and add a s [...] discards 01811153e round-robin-notify.sh: Move single_commit_p() here adds 2be6134fd round-robin-notify.sh: Move single_commit_p() here 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 (cbdfc4484) \ N -- N -- N refs/changes/91/44491/1 (2be6134fd) 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 | 647 ------------------------- round-robin-notify.sh | 1257 ------------------------------------------------- 2 files changed, 1904 deletions(-) delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh -- 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/91/44191/3 updated (23fcda0f2 -> 6d8c0b0df)

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/91/44191/3 in repository toolchain/jenkins-scripts. discards 23fcda0f2 round-robin-notify.sh: Add print_result print_config and use [...] discards bfab9fc06 round-robin-notify.sh: split update and post interesting_commits discards 8d1ed2ff0 round-robin-notify.sh: print_mail_recipients discards dfa9c6580 round-robin-notify.sh: Add print_commits discards fd1a7b774 round-robin-notify.sh: Adding --notify parameter discards 22caef4d3 jenkins-helpers.sh: Fix get_baseline_manifest adds 6d8c0b0df jenkins-helpers.sh: Fix get_baseline_manifest 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 (23fcda0f2) \ N -- N -- N refs/changes/91/44191/3 (6d8c0b0df) 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 | 633 -------------------------- round-robin-notify.sh | 1210 ------------------------------------------------- 2 files changed, 1843 deletions(-) delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh -- 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/91/44191/2 updated (9b59f8245 -> 6d8c0b0df)

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/91/44191/2 in repository toolchain/jenkins-scripts. discards 9b59f8245 round-robin-notify.sh: Add print_result print_config and use [...] discards 20a738493 round-robin-notify.sh: split update and post interesting_commits discards 4605a53ba round-robin-notify.sh: print_mail_recipients discards dfa9c6580 round-robin-notify.sh: Add print_commits discards fd1a7b774 round-robin-notify.sh: Adding --notify parameter discards 22caef4d3 jenkins-helpers.sh: Fix get_baseline_manifest adds 6d8c0b0df jenkins-helpers.sh: Fix get_baseline_manifest 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 (9b59f8245) \ N -- N -- N refs/changes/91/44191/2 (6d8c0b0df) 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 | 633 -------------------------- round-robin-notify.sh | 1210 ------------------------------------------------- 2 files changed, 1843 deletions(-) delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh -- 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/91/44191/1 updated (8f9b0b620 -> 31ac4c7c3)

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/91/44191/1 in repository toolchain/jenkins-scripts. discards 8f9b0b620 round-robin-notify.sh: Add print_result print_config and use [...] discards 87da6e4e0 round-robin-notify.sh: split update and post interesting_commits discards a13ad33ce round-robin-notify.sh: print_mail_recipients discards 24a3cfec6 round-robin-notify.sh: Add print_commits discards d3105f260 round-robin.sh: Add results_date to manifest.sh new 31ac4c7c3 round-robin.sh: Add results_date to manifest.sh 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 (8f9b0b620) \ N -- N -- N refs/changes/91/44191/1 (31ac4c7c3) 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: round-robin-bisect.sh | 633 ------------------------- round-robin-notify.sh | 1216 ------------------------------------------------- 2 files changed, 1849 deletions(-) delete mode 100755 round-robin-bisect.sh delete mode 100755 round-robin-notify.sh -- 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/91/44091/2 updated (9b44225da -> c6d16c4d5)

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/91/44091/2 in repository toolchain/jenkins-scripts. discards 9b44225da tcwg_aosp-build.sh: Allow to specify a custom shadow_bin directory new c6d16c4d5 tcwg_aosp-build.sh: Allow to specify a custom shadow_bin directory 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 (9b44225da) \ N -- N -- N refs/changes/91/44091/2 (c6d16c4d5) 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/91/44091/1 updated (8278e29e5 -> 84f6bea77)

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/91/44091/1 in repository toolchain/jenkins-scripts. discards 8278e29e5 tcwg_aosp-build.sh: Allow to specify a custom shadow_bin directory new 84f6bea77 tcwg_aosp-build.sh: Allow to specify a custom shadow_bin directory 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 (8278e29e5) \ N -- N -- N refs/changes/91/44091/1 (84f6bea77) 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/91/43891/5 updated (8a60fe784 -> be970c581)

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/91/43891/5 in repository toolchain/jenkins-scripts. discards 8a60fe784 shadow-cc.sh: Allow use of custom cflags for shadow builds adds be970c581 shadow-cc.sh: Allow use of custom cflags for shadow builds 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 (8a60fe784) \ N -- N -- N refs/changes/91/43891/5 (be970c581) 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/91/43891/4 updated (2bf8d30ee -> ae9fdb0ae)

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/91/43891/4 in repository toolchain/jenkins-scripts. discards 2bf8d30ee shadow-cc.sh: Allow use of custom cflags for shadow builds new ae9fdb0ae shadow-cc.sh: Allow use of custom cflags for shadow builds 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 (2bf8d30ee) \ N -- N -- N refs/changes/91/43891/4 (ae9fdb0ae) 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/91/43891/3 updated (70be54116 -> f16c79bc7)

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/91/43891/3 in repository toolchain/jenkins-scripts. discards 70be54116 shadow-cc.sh: Allow use of custom cflags for shadow builds adds f16c79bc7 shadow-cc.sh: Allow use of custom cflags for shadow builds 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 (70be54116) \ N -- N -- N refs/changes/91/43891/3 (f16c79bc7) 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/91/43891/2 updated (7845c4c94 -> 7e048fbe0)

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/91/43891/2 in repository toolchain/jenkins-scripts. discards 7845c4c94 shadow-cc.sh: Allow use of custom cflags for shadow builds new 7e048fbe0 shadow-cc.sh: Allow use of custom cflags for shadow builds 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 (7845c4c94) \ N -- N -- N refs/changes/91/43891/2 (7e048fbe0) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024