Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/29/30829/1 updated (5a0e2ea9b -> a2ab659fb)

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/29/30829/1 in repository toolchain/jenkins-scripts. discards 5a0e2ea9b Merge branch 'master' into tcwg_bmk adds a2ab659fb Merge branch 'master' into tcwg_bmk 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 (5a0e2ea9b) \ N -- N -- N refs/changes/29/30829/1 (a2ab659fb) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/30529/3 updated (80ad925f2 -> 60225c591)

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/29/30529/3 in repository toolchain/jenkins-scripts. discards 80ad925f2 tcwg_bmk-build.sh: Use ABE's sysroot and binutils for LLVM's build adds 60225c591 tcwg_bmk-build.sh: Use ABE's sysroot and binutils for LLVM's 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 (80ad925f2) \ N -- N -- N refs/changes/29/30529/3 (60225c591) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/30529/2 updated (4aa54a636 -> 173eec74d)

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/29/30529/2 in repository toolchain/jenkins-scripts. discards 4aa54a636 tcwg_bmk-build.sh: Use ABE's sysroot and binutils for LLVM's build new 173eec74d tcwg_bmk-build.sh: Use ABE's sysroot and binutils for LLVM's 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 (4aa54a636) \ N -- N -- N refs/changes/29/30529/2 (173eec74d) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/30529/1 updated (0e77324cf -> 249d62771)

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/29/30529/1 in repository toolchain/jenkins-scripts. discards 0e77324cf tcwg_bmk-build.sh: Use ABE's sysroot and binutils for LLVM's build adds 249d62771 tcwg_bmk-build.sh: Use ABE's sysroot and binutils for LLVM's 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 (0e77324cf) \ N -- N -- N refs/changes/29/30529/1 (249d62771) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/29829/1 updated (fd7d61fd7 -> 8e46dcb27)

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/29/29829/1 in repository toolchain/jenkins-scripts. discards fd7d61fd7 Save WIP new 8e46dcb27 Save WIP 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 (fd7d61fd7) \ N -- N -- N refs/changes/29/29829/1 (8e46dcb27) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/29429/3 updated (80a6ec676 -> b6bef442a)

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/29/29429/3 in repository toolchain/jenkins-scripts. discards 80a6ec676 tcwg_kernel-build.sh: Make reset_artifacts depend only on ${rr[]} adds b6bef442a tcwg_kernel-build.sh: Make reset_artifacts depend only on ${rr[]} 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 (80a6ec676) \ N -- N -- N refs/changes/29/29429/3 (b6bef442a) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/29429/2 updated (658a56130 -> ef52d611a)

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/29/29429/2 in repository toolchain/jenkins-scripts. discards 658a56130 tcwg_kernel-build.sh: Make clone_repo depend only on ${rr[]} new ef52d611a tcwg_kernel-build.sh: Make clone_repo depend only on ${rr[]} 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 (658a56130) \ N -- N -- N refs/changes/29/29429/2 (ef52d611a) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/29429/1 updated (ecd60d039 -> 775fab648)

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/29/29429/1 in repository toolchain/jenkins-scripts. discards ecd60d039 tcwg_kernel-build.sh: Make reset_artifacts depend only on ${rr[]} adds 775fab648 tcwg_kernel-build.sh: Make reset_artifacts depend only on ${rr[]} 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 (ecd60d039) \ N -- N -- N refs/changes/29/29429/1 (775fab648) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/28/47228/2 updated (4bde48ce0 -> 64d6faf6c)

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/28/47228/2 in repository toolchain/jenkins-scripts. discards 4bde48ce0 pw-helpers.sh (pw_patch_check_state): Handle multi-page "chec [...] adds 64d6faf6c pw-helpers.sh (pw_patch_check_state): Handle multi-page "chec [...] 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 (4bde48ce0) \ N -- N -- N refs/changes/28/47228/2 (64d6faf6c) 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, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/28/47228/1 updated (3e231f7fa -> e4f0582b8)

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/28/47228/1 in repository toolchain/jenkins-scripts. discards 3e231f7fa pw-helpers.sh (pw_patch_check_state): Handle multi-page "chec [...] new e4f0582b8 pw-helpers.sh (pw_patch_check_state): Handle multi-page "chec [...] 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 (3e231f7fa) \ N -- N -- N refs/changes/28/47228/1 (e4f0582b8) 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, 2 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024