Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/68/47068/2 updated (6611a5de4 -> c4c6e8c05)

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/68/47068/2 in repository toolchain/jenkins-scripts. discards 6611a5de4 start-container-docker.sh: Make an exception for WSL precommit mount adds c4c6e8c05 start-container-docker.sh: Make an exception for WSL precommit mount 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 (6611a5de4) \ N -- N -- N refs/changes/68/47068/2 (c4c6e8c05) 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/68/47068/1 updated (c50b5a7a4 -> f2de566cf)

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/68/47068/1 in repository toolchain/jenkins-scripts. discards c50b5a7a4 start-container-docker.sh: Make an exception for WSL precommit mount new f2de566cf start-container-docker.sh: Make an exception for WSL precommit mount 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 (c50b5a7a4) \ N -- N -- N refs/changes/68/47068/1 (f2de566cf) 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/68/46968/1 updated (a298a0775 -> b28531c7c)

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/68/46968/1 in repository toolchain/jenkins-scripts. discards a298a0775 tcwg_chromium-build.sh: remove useless _dir write adds b28531c7c tcwg_chromium-build.sh: remove useless _dir write 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 (a298a0775) \ N -- N -- N refs/changes/68/46968/1 (b28531c7c) 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/68/46668/2 updated (70f80beb2 -> 099d6021e)

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/68/46668/2 in repository toolchain/jenkins-scripts. discards 70f80beb2 tcwg-update-lnt-results.sh: extract lnt reports in reverse order adds 099d6021e tcwg-update-lnt-results.sh: extract lnt reports in reverse order 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 (70f80beb2) \ N -- N -- N refs/changes/68/46668/2 (099d6021e) 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/68/46668/1 updated (247414a1f -> ce39fbc2b)

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/68/46668/1 in repository toolchain/jenkins-scripts. discards 247414a1f tcwg-update-lnt-results.sh: extract lnt reports in reverse order new ce39fbc2b tcwg-update-lnt-results.sh: extract lnt reports in reverse order 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 (247414a1f) \ N -- N -- N refs/changes/68/46668/1 (ce39fbc2b) 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/68/46068/1 updated (82a54ab83 -> b9194e230)

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/68/46068/1 in repository toolchain/jenkins-scripts. discards 82a54ab83 tcwg_gnu-build.sh: Workaround rewrite artifact adds b9194e230 tcwg_gnu-build.sh: Workaround rewrite artifact 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 (82a54ab83) \ N -- N -- N refs/changes/68/46068/1 (b9194e230) 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/68/45668/1 updated (7c9f521f1 -> f097e6fb5)

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/68/45668/1 in repository toolchain/jenkins-scripts. discards 7c9f521f1 round-robin-baseline.sh (rewrite_single_revision): Fetch annex discards 381ac9376 pw-apply.sh: Improve application of GCC patches adds f097e6fb5 pw-apply.sh: Improve application of GCC patches 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 (7c9f521f1) \ N -- N -- N refs/changes/68/45668/1 (f097e6fb5) 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-baseline.sh | 456 ------------ round-robin-bisect.sh | 655 ------------------ round-robin-notify.sh | 1754 ----------------------------------------------- 3 files changed, 2865 deletions(-) delete mode 100755 round-robin-baseline.sh 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/68/44768/3 updated (731e34001 -> ac5a96c78)

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/68/44768/3 in repository toolchain/jenkins-scripts. discards 731e34001 tcwg_gnu-build.sh: Apply GDB patch adding configure option to [...] adds ac5a96c78 tcwg_gnu-build.sh: Apply GDB patch adding configure option to [...] 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 (731e34001) \ N -- N -- N refs/changes/68/44768/3 (ac5a96c78) 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/68/44768/2 updated (a07687d64 -> b0c078235)

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/68/44768/2 in repository toolchain/jenkins-scripts. discards a07687d64 tcwg_gnu-build.sh: Apply GDB patch adding configure option to [...] new b0c078235 tcwg_gnu-build.sh: Apply GDB patch adding configure option to [...] 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 (a07687d64) \ N -- N -- N refs/changes/68/44768/2 (b0c078235) 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/68/44768/1 updated (5c1ca17a1 -> 7af5a4748)

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/68/44768/1 in repository toolchain/jenkins-scripts. discards 5c1ca17a1 tcwg_gnu-build.sh: Apply GDB patch adding configure option to [...] new 7af5a4748 tcwg_gnu-build.sh: Apply GDB patch adding configure option to [...] 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 (5c1ca17a1) \ N -- N -- N refs/changes/68/44768/1 (7af5a4748) 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