Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/94/47194/1 updated (131b80371 -> 15c0faa5d)

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/94/47194/1 in repository toolchain/jenkins-scripts. discards 131b80371 tcwg_chromium-build.sh: remove build dir adds 15c0faa5d tcwg_chromium-build.sh: remove build dir 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 (131b80371) \ N -- N -- N refs/changes/94/47194/1 (15c0faa5d) 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/94/46594/2 updated (97148fca4 -> 5aaddda9f)

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/94/46594/2 in repository toolchain/jenkins-scripts. discards 97148fca4 round-robin.sh (build_abe): Remove testresults/ before creating it adds 5aaddda9f round-robin.sh (build_abe): Remove testresults/ before creating it 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 (97148fca4) \ N -- N -- N refs/changes/94/46594/2 (5aaddda9f) 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/94/46594/1 updated (afc14b5eb -> 0b84430ef)

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/94/46594/1 in repository toolchain/jenkins-scripts. discards afc14b5eb round-robin.sh (build_abe): Remove testresults/ before creating it new 0b84430ef round-robin.sh (build_abe): Remove testresults/ before creating it 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 (afc14b5eb) \ N -- N -- N refs/changes/94/46594/1 (0b84430ef) 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/94/46194/4 updated (077e10ea8 -> 046f66f9b)

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/94/46194/4 in repository toolchain/jenkins-scripts. discards 077e10ea8 tcwg-lnt/create-server.sh: always update lnt sources on serve [...] adds 046f66f9b tcwg-lnt/create-server.sh: always update lnt sources on serve [...] 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 (077e10ea8) \ N -- N -- N refs/changes/94/46194/4 (046f66f9b) 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/94/46194/3 updated (ee9e97a71 -> 1986bc6b6)

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/94/46194/3 in repository toolchain/jenkins-scripts. discards ee9e97a71 tcwg-lnt/create-server.sh: always update lnt sources on serve [...] new 1986bc6b6 tcwg-lnt/create-server.sh: always update lnt sources on serve [...] 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 (ee9e97a71) \ N -- N -- N refs/changes/94/46194/3 (1986bc6b6) 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/94/46194/2 updated (72c8496ee -> 1801c3669)

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/94/46194/2 in repository toolchain/jenkins-scripts. discards 72c8496ee tcwg-lnt/create-server.sh: always update lnt sources on serve [...] new 1801c3669 tcwg-lnt/create-server.sh: always update lnt sources on serve [...] 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 (72c8496ee) \ N -- N -- N refs/changes/94/46194/2 (1801c3669) 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/94/46194/1 updated (3ec87d120 -> 2a1144384)

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/94/46194/1 in repository toolchain/jenkins-scripts. discards 3ec87d120 tcwg-lnt/create-server.sh: always update jenkins scripts on s [...] new 2a1144384 tcwg-lnt/create-server.sh: always update jenkins scripts on s [...] 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 (3ec87d120) \ N -- N -- N refs/changes/94/46194/1 (2a1144384) 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/94/45894/7 updated (e6ae1013a -> d5f074b01)

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/94/45894/7 in repository toolchain/jenkins-scripts. discards e6ae1013a tcwg_gnu-config.sh: Use gnu_data array instead of global variables adds d5f074b01 tcwg_gnu-config.sh: Use gnu_data array instead of global variables 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 (e6ae1013a) \ N -- N -- N refs/changes/94/45894/7 (d5f074b01) 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/94/45894/6 updated (77e78aafa -> 5a9ef6cbf)

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/94/45894/6 in repository toolchain/jenkins-scripts. discards 77e78aafa tcwg_gnu-config.sh: Use gnu_data array instead of global variables new 5a9ef6cbf tcwg_gnu-config.sh: Use gnu_data array instead of global variables 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 (77e78aafa) \ N -- N -- N refs/changes/94/45894/6 (5a9ef6cbf) 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/94/45894/5 updated (93c405489 -> dd235c8ac)

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/94/45894/5 in repository toolchain/jenkins-scripts. discards 93c405489 tcwg_gnu-config.sh: Use gnu_data array instead of global variables new dd235c8ac tcwg_gnu-config.sh: Use gnu_data array instead of global variables 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 (93c405489) \ N -- N -- N refs/changes/94/45894/5 (dd235c8ac) 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