Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/37/33937/2 updated (42e99f8d0 -> c87fa0d70)

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/33937/2 in repository toolchain/jenkins-scripts. discards 42e99f8d0 abe-bisect.sh: Add support for good and bad revs as git revs adds c87fa0d70 abe-bisect.sh: Add support for good and bad revs as git revs 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 (42e99f8d0) \ N -- N -- N refs/changes/37/33937/2 (c87fa0d70) 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/33937/1 updated (9938319b0 -> 855506e8f)

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/33937/1 in repository toolchain/jenkins-scripts. discards 9938319b0 abe-bisect.sh: Add support for good and bad revs as git revs new 855506e8f abe-bisect.sh: Add support for good and bad revs as git revs 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 (9938319b0) \ N -- N -- N refs/changes/37/33937/1 (855506e8f) 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/37/32637/1 updated (22e6957fd -> daa847f3c)

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/32637/1 in repository toolchain/jenkins-scripts. discards 22e6957fd jenkins-helpers.sh: Bind-mount ssh host keys adds daa847f3c jenkins-helpers.sh: Bind-mount ssh host keys 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 (22e6957fd) \ N -- N -- N refs/changes/37/32637/1 (daa847f3c) 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/32337/1 updated (a826257a9 -> 4de5163cd)

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/32337/1 in repository toolchain/jenkins-scripts. discards a826257a9 Debug change adds 4de5163cd Debug change 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 (a826257a9) \ N -- N -- N refs/changes/37/32337/1 (4de5163cd) 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/31137/1 updated (ae22724f7 -> 58cd4f046)

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/31137/1 in repository toolchain/jenkins-scripts. discards ae22724f7 tcwg_bmk-build.sh: Fix thinko; we don't resolve @hw_type@ locally adds 58cd4f046 tcwg_bmk-build.sh: Fix thinko; we don't resolve @hw_type@ locally 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 (ae22724f7) \ N -- N -- N refs/changes/37/31137/1 (58cd4f046) 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/30737/2 updated (7404092ad -> 31d3f7ccf)

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/30737/2 in repository toolchain/jenkins-scripts. discards 7404092ad tcwg-benchmark.sh: Add support for clean_older_than adds 31d3f7ccf tcwg-benchmark.sh: Add support for clean_older_than 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 (7404092ad) \ N -- N -- N refs/changes/37/30737/2 (31d3f7ccf) 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/30737/1 updated (12a474bae -> c6b0a3a40)

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/30737/1 in repository toolchain/jenkins-scripts. discards 12a474bae tcwg-benchmark.sh: Add support for clean_older_than new c6b0a3a40 tcwg-benchmark.sh: Add support for clean_older_than 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 (12a474bae) \ N -- N -- N refs/changes/37/30737/1 (c6b0a3a40) 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/37/30637/3 updated (258dc2d14 -> 5969b34cd)

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/30637/3 in repository toolchain/jenkins-scripts. discards 258dc2d14 round-robin.sh: Workaround re-writes of base-artifacts.git history adds 5969b34cd round-robin.sh: Workaround re-writes of base-artifacts.git history 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 (258dc2d14) \ N -- N -- N refs/changes/37/30637/3 (5969b34cd) 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/30637/2 updated (a930c737b -> 7441f94fc)

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/30637/2 in repository toolchain/jenkins-scripts. discards a930c737b round-robin.sh: Workaround re-writes of base-artifacts.git history new 7441f94fc round-robin.sh: Workaround re-writes of base-artifacts.git history 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 (a930c737b) \ N -- N -- N refs/changes/37/30637/2 (7441f94fc) 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/37/30637/1 updated (ce39f0e76 -> 3b70c04de)

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/30637/1 in repository toolchain/jenkins-scripts. discards ce39f0e76 round-robin.sh: Workaround re-writes of base-artifacts.git history new 3b70c04de round-robin.sh: Workaround re-writes of base-artifacts.git history 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 (ce39f0e76) \ N -- N -- N refs/changes/37/30637/1 (3b70c04de) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024