Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/37/29837/3 updated (0c835eb19 -> 35711786e)

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/37/29837/3 in repository toolchain/jenkins-scripts. discards 0c835eb19 round-robin.sh: Make clone_repo clean repos during bisect builds adds 35711786e round-robin.sh: Make clone_repo clean repos during bisect builds 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 (0c835eb19) \ N -- N -- N refs/changes/37/29837/3 (35711786e) 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/37/29837/2 updated (498c9715b -> 8a2c69b02)

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/37/29837/2 in repository toolchain/jenkins-scripts. discards 498c9715b round-robin.sh: Make clone_repo clean repos during bisect builds adds 8a2c69b02 round-robin.sh: Make clone_repo clean repos during bisect builds 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 (498c9715b) \ N -- N -- N refs/changes/37/29837/2 (8a2c69b02) 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/37/29837/1 updated (59fa8f14f -> e94062384)

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/37/29837/1 in repository toolchain/jenkins-scripts. discards 59fa8f14f round-robin.sh: Make clone_repo clean repos during bisect builds adds e94062384 round-robin.sh: Make clone_repo clean repos during bisect builds 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 (59fa8f14f) \ N -- N -- N refs/changes/37/29837/1 (e94062384) 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/36/47336/5 updated (25b5c0c8d -> cf6834653)

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/36/47336/5 in repository toolchain/jenkins-scripts. discards 25b5c0c8d tcwg-wip/split-repo*: Support to split jenkins-scripts new cf6834653 tcwg-wip/split-repo*: Support to split jenkins-scripts 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 (25b5c0c8d) \ N -- N -- N refs/changes/36/47336/5 (cf6834653) 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/36/47336/4 updated (d75aae7fe -> d5ee2c289)

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/36/47336/4 in repository toolchain/jenkins-scripts. discards d75aae7fe tcwg-wip/split-repo*: Support to split jenkins-scripts new d5ee2c289 tcwg-wip/split-repo*: Support to split jenkins-scripts 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 (d75aae7fe) \ N -- N -- N refs/changes/36/47336/4 (d5ee2c289) 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/36/47336/3 updated (1f4f4b234 -> 3f708aef7)

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/36/47336/3 in repository toolchain/jenkins-scripts. discards 1f4f4b234 tcwg-wip/split-repo*: Support to split jenkins-scripts new 3f708aef7 tcwg-wip/split-repo*: Support to split jenkins-scripts 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 (1f4f4b234) \ N -- N -- N refs/changes/36/47336/3 (3f708aef7) 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/36/47336/2 updated (98ae5d1fd -> 749992406)

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/36/47336/2 in repository toolchain/jenkins-scripts. discards 98ae5d1fd tcwg-wip/split-repo*: Support to split jenkins-scripts new 749992406 tcwg-wip/split-repo*: Support to split jenkins-scripts 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 (98ae5d1fd) \ N -- N -- N refs/changes/36/47336/2 (749992406) 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/36/47336/1 updated (741c45176 -> c9f73ab25)

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/36/47336/1 in repository toolchain/jenkins-scripts. discards 741c45176 tcwg-wip/split-repo*: Support to split jenkins-scripts new c9f73ab25 tcwg-wip/split-repo*: Support to split jenkins-scripts 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 (741c45176) \ N -- N -- N refs/changes/36/47336/1 (c9f73ab25) 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/36/47136/1 updated (8fda517b1 -> 8db106290)

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/36/47136/1 in repository toolchain/jenkins-scripts. discards 8fda517b1 tcwg_chromium-build.sh: Re-enable autotest adds 8db106290 tcwg_chromium-build.sh: Re-enable autotest 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 (8fda517b1) \ N -- N -- N refs/changes/36/47136/1 (8db106290) 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/36/46936/1 updated (04b8eedd6 -> a8bbfd077)

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/36/46936/1 in repository toolchain/jenkins-scripts. discards 04b8eedd6 tcwg_chromium-build.sh: Enable ci_autotest adds a8bbfd077 tcwg_chromium-build.sh: Enable ci_autotest 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 (04b8eedd6) \ N -- N -- N refs/changes/36/46936/1 (a8bbfd077) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024