Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/52/35252/8 updated (8cddf6df4 -> 761866cda)

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/52/35252/8 in repository toolchain/jenkins-scripts. discards 8cddf6df4 tcwg_bmk-build.sh/tcwg_gnu-build.sh: Mark expected exits adds 761866cda tcwg_bmk-build.sh/tcwg_gnu-build.sh: Mark expected exits 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 (8cddf6df4) \ N -- N -- N refs/changes/52/35252/8 (761866cda) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/35252/7 updated (b1bfdb541 -> 637613d6b)

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/52/35252/7 in repository toolchain/jenkins-scripts. discards b1bfdb541 tcwg_bmk-build.sh/tcwg_gnu-build.sh: Mark expected exits adds 637613d6b tcwg_bmk-build.sh/tcwg_gnu-build.sh: Mark expected exits 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 (b1bfdb541) \ N -- N -- N refs/changes/52/35252/7 (637613d6b) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/35252/6 updated (593d03cba -> 5b56b0321)

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/52/35252/6 in repository toolchain/jenkins-scripts. discards 593d03cba tcwg_bmk-build.sh/tcwg_gnu-build.sh: Mark expected exits new 5b56b0321 tcwg_bmk-build.sh/tcwg_gnu-build.sh: Mark expected exits 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 (593d03cba) \ N -- N -- N refs/changes/52/35252/6 (5b56b0321) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/35252/5 updated (098715548 -> 9bdc4ee2c)

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/52/35252/5 in repository toolchain/jenkins-scripts. discards 098715548 tcwg_bmk-build.sh/tcwg_gnu-build.sh: Mark expected exits new 9bdc4ee2c tcwg_bmk-build.sh/tcwg_gnu-build.sh: Mark expected exits 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 (098715548) \ N -- N -- N refs/changes/52/35252/5 (9bdc4ee2c) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/35252/4 updated (5efc49d9b -> 05a614a1d)

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/52/35252/4 in repository toolchain/jenkins-scripts. discards 5efc49d9b tcwg_bmk-build.sh/tcwg_gnu-build.sh: Mark expected exits new 05a614a1d tcwg_bmk-build.sh/tcwg_gnu-build.sh: Mark expected exits 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 (5efc49d9b) \ N -- N -- N refs/changes/52/35252/4 (05a614a1d) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/35252/3 updated (8b74aa9e0 -> a4d20839b)

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/52/35252/3 in repository toolchain/jenkins-scripts. discards 8b74aa9e0 tcwg_bmk-build.sh: Don't trap EXIT signal new a4d20839b tcwg_bmk-build.sh: Don't trap EXIT signal 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 (8b74aa9e0) \ N -- N -- N refs/changes/52/35252/3 (a4d20839b) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/35252/2 updated (433e46a27 -> 95fe6a92b)

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/52/35252/2 in repository toolchain/jenkins-scripts. discards 433e46a27 tcwg_bmk-build.sh: Don't trap EXIT signal adds 95fe6a92b tcwg_bmk-build.sh: Don't trap EXIT signal 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 (433e46a27) \ N -- N -- N refs/changes/52/35252/2 (95fe6a92b) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/35252/1 updated (01968bbbf -> 2b9b16297)

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/52/35252/1 in repository toolchain/jenkins-scripts. discards 01968bbbf tcwg_bmk-build.sh: Don't trap EXIT signal new 2b9b16297 tcwg_bmk-build.sh: Don't trap EXIT signal 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 (01968bbbf) \ N -- N -- N refs/changes/52/35252/1 (2b9b16297) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/34152/2 updated (e2196e583 -> 6cd2f12ab)

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/52/34152/2 in repository toolchain/jenkins-scripts. discards e2196e583 Revert "tcwg-update-tested.sh: Force push to abe.git and jenk [...] adds 6cd2f12ab Revert "tcwg-update-tested.sh: Force push to abe.git and jenk [...] 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 (e2196e583) \ N -- N -- N refs/changes/52/34152/2 (6cd2f12ab) 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, 4 weeks

[toolchain/jenkins-scripts] reference refs/changes/52/34152/1 updated (a8ef2e80b -> 99283e39c)

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/52/34152/1 in repository toolchain/jenkins-scripts. discards a8ef2e80b Revert "tcwg-update-tested.sh: Force push to abe.git and jenk [...] new 99283e39c Revert "tcwg-update-tested.sh: Force push to abe.git and jenk [...] 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 (a8ef2e80b) \ N -- N -- N refs/changes/52/34152/1 (99283e39c) 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, 4 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024