Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/89/38589/5 updated (70b69667a -> 9fa0ea442)

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/89/38589/5 in repository toolchain/jenkins-scripts. discards 70b69667a tcwg-benchmark.sh: Update handling of hw_tag in results_id adds 9fa0ea442 tcwg-benchmark.sh: Update handling of hw_tag in results_id 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 (70b69667a) \ N -- N -- N refs/changes/89/38589/5 (9fa0ea442) 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/89/38589/4 updated (4c71990a0 -> 4f3733128)

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/89/38589/4 in repository toolchain/jenkins-scripts. discards 4c71990a0 tcwg-benchmark.sh: Update handling of hw_tag in results_id adds 4f3733128 tcwg-benchmark.sh: Update handling of hw_tag in results_id 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 (4c71990a0) \ N -- N -- N refs/changes/89/38589/4 (4f3733128) 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/89/38589/3 updated (82fcd0f9b -> a399cc3a0)

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/89/38589/3 in repository toolchain/jenkins-scripts. discards 82fcd0f9b tcwg-benchmark.sh: Update handling of hw_tag in results_id adds a399cc3a0 tcwg-benchmark.sh: Update handling of hw_tag in results_id 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 (82fcd0f9b) \ N -- N -- N refs/changes/89/38589/3 (a399cc3a0) 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/89/38589/2 updated (6a3471002 -> c16b1d2c6)

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/89/38589/2 in repository toolchain/jenkins-scripts. discards 6a3471002 tcwg-benchmark.sh: Update handling of hw_tag in results_id adds c16b1d2c6 tcwg-benchmark.sh: Update handling of hw_tag in results_id 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 (6a3471002) \ N -- N -- N refs/changes/89/38589/2 (c16b1d2c6) 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/89/38589/1 updated (003cbd68e -> d91baa60d)

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/89/38589/1 in repository toolchain/jenkins-scripts. discards 003cbd68e tcwg-benchmark.sh: Update handling of hw_tag in results_id new d91baa60d tcwg-benchmark.sh: Update handling of hw_tag in results_id 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 (003cbd68e) \ N -- N -- N refs/changes/89/38589/1 (d91baa60d) 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/89/38189/5 updated (8f2393f9d -> fc5811f7a)

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/89/38189/5 in repository toolchain/jenkins-scripts. discards 8f2393f9d start-container-docker.sh: Move workaround for dockerhub's limits adds fc5811f7a start-container-docker.sh: Move workaround for dockerhub's limits 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 (8f2393f9d) \ N -- N -- N refs/changes/89/38189/5 (fc5811f7a) 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/89/38189/4 updated (88825d472 -> 2a7591d5d)

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/89/38189/4 in repository toolchain/jenkins-scripts. discards 88825d472 start-container-docker.sh: Move workaround for dockerhub's limits adds 2a7591d5d start-container-docker.sh: Move workaround for dockerhub's limits 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 (88825d472) \ N -- N -- N refs/changes/89/38189/4 (2a7591d5d) 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/89/38189/3 updated (806241479 -> 2a2449c5b)

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/89/38189/3 in repository toolchain/jenkins-scripts. discards 806241479 start-container-docker.sh: Move workaround for dockerhub's limits adds 2a2449c5b start-container-docker.sh: Move workaround for dockerhub's limits 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 (806241479) \ N -- N -- N refs/changes/89/38189/3 (2a2449c5b) 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/89/38189/2 updated (f154a9e51 -> 24383c68f)

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/89/38189/2 in repository toolchain/jenkins-scripts. discards f154a9e51 start-container-docker.sh: Move workaround for dockerhub's limits new 24383c68f start-container-docker.sh: Move workaround for dockerhub's limits 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 (f154a9e51) \ N -- N -- N refs/changes/89/38189/2 (24383c68f) 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/89/38189/1 updated (d7b75e5a3 -> 2859b8d20)

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/89/38189/1 in repository toolchain/jenkins-scripts. discards d7b75e5a3 start-container-docker.sh: Move workaround for dockerhub's limits new 2859b8d20 start-container-docker.sh: Move workaround for dockerhub's limits 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 (d7b75e5a3) \ N -- N -- N refs/changes/89/38189/1 (2859b8d20) 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