Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/03/45703/2 updated (3dda0bb08 -> ead51574c)

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/03/45703/2 in repository toolchain/jenkins-scripts. discards 3dda0bb08 round-robin-notify.sh (gnu_print_result): Improve --long version discards e29a02204 round-robin-notify.sh (print_mail_body): Add more ways to con [...] discards c21c34105 round-robin-baseline.sh (rewrite_single_revision): Add assert discards 197d50292 tcwg_gnu-build.sh: Bump minor version to update jira cards adds ead51574c tcwg_gnu-build.sh: Bump minor version to update jira cards 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 (3dda0bb08) \ N -- N -- N refs/changes/03/45703/2 (ead51574c) 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 | 524 -------------- round-robin-bisect.sh | 655 ------------------ round-robin-notify.sh | 1739 ----------------------------------------------- 3 files changed, 2918 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/03/45703/1 updated (e7c19cdd6 -> ead51574c)

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/03/45703/1 in repository toolchain/jenkins-scripts. discards e7c19cdd6 round-robin-notify.sh (gnu_print_result): Improve --long version discards c5eff2fce round-robin-notify.sh (print_mail_body): Add more ways to con [...] discards 197d50292 tcwg_gnu-build.sh: Bump minor version to update jira cards adds ead51574c tcwg_gnu-build.sh: Bump minor version to update jira cards 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 (e7c19cdd6) \ N -- N -- N refs/changes/03/45703/1 (ead51574c) 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 | 516 -------------- round-robin-bisect.sh | 655 ------------------ round-robin-notify.sh | 1739 ----------------------------------------------- 3 files changed, 2910 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/03/44803/8 updated (14a3d38ea -> f7ec29736)

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/03/44803/8 in repository toolchain/jenkins-scripts. discards 14a3d38ea tcwg_bmk-build.sh: Revert storing bmk-data in annex adds f7ec29736 tcwg_bmk-build.sh: Revert storing bmk-data in annex 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 (14a3d38ea) \ N -- N -- N refs/changes/03/44803/8 (f7ec29736) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/03/44803/7 updated (04b1e8c68 -> 28108b734)

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/03/44803/7 in repository toolchain/jenkins-scripts. discards 04b1e8c68 tcwg_bmk-build.sh: Revert storing bmk-data in annex new 28108b734 tcwg_bmk-build.sh: Revert storing bmk-data in annex 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 (04b1e8c68) \ N -- N -- N refs/changes/03/44803/7 (28108b734) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/03/44803/6 updated (b1e45e3b2 -> 25fd4a20b)

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/03/44803/6 in repository toolchain/jenkins-scripts. discards b1e45e3b2 tcwg_bmk-build.sh: Revert storing bmk-data in annex new 25fd4a20b tcwg_bmk-build.sh: Revert storing bmk-data in annex 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 (b1e45e3b2) \ N -- N -- N refs/changes/03/44803/6 (25fd4a20b) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/03/44803/5 updated (37ea4c8a9 -> 7694fe34c)

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/03/44803/5 in repository toolchain/jenkins-scripts. discards 37ea4c8a9 tcwg_bmk-build.sh: Revert storing bmk-data in annex new 7694fe34c tcwg_bmk-build.sh: Revert storing bmk-data in annex 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 (37ea4c8a9) \ N -- N -- N refs/changes/03/44803/5 (7694fe34c) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/03/44803/4 updated (2ae1163d0 -> ab9e826ca)

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/03/44803/4 in repository toolchain/jenkins-scripts. discards 2ae1163d0 tcwg_bmk-build.sh: Revert storing bmk-data in annex new ab9e826ca tcwg_bmk-build.sh: Revert storing bmk-data in annex 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 (2ae1163d0) \ N -- N -- N refs/changes/03/44803/4 (ab9e826ca) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/03/44803/3 updated (838dec2ad -> 52da47983)

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/03/44803/3 in repository toolchain/jenkins-scripts. discards 838dec2ad tcwg_bmk-build.sh: Revert storing bmk-data in annex new 52da47983 tcwg_bmk-build.sh: Revert storing bmk-data in annex 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 (838dec2ad) \ N -- N -- N refs/changes/03/44803/3 (52da47983) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/03/44803/2 updated (e49b63e2a -> 4414e3299)

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/03/44803/2 in repository toolchain/jenkins-scripts. discards e49b63e2a tcwg_bmk-build.sh: Revert storing bmk-data in annex new 4414e3299 tcwg_bmk-build.sh: Revert storing bmk-data in annex 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 (e49b63e2a) \ N -- N -- N refs/changes/03/44803/2 (4414e3299) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/03/44803/1 updated (fa8ef8856 -> 12b8542c9)

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/03/44803/1 in repository toolchain/jenkins-scripts. discards fa8ef8856 tcwg_bmk-build.sh: Revert storing bmk-data in annex new 12b8542c9 tcwg_bmk-build.sh: Revert storing bmk-data in annex 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 (fa8ef8856) \ N -- N -- N refs/changes/03/44803/1 (12b8542c9) 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.

4 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024