Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/60/33960/4 updated (4ff20df01 -> 05ea2d209)

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/60/33960/4 in repository toolchain/jenkins-scripts. discards 4ff20df01 tcwg_bmk-build.sh: Require setting ci_project adds 05ea2d209 tcwg_bmk-build.sh: Require setting ci_project 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 (4ff20df01) \ N -- N -- N refs/changes/60/33960/4 (05ea2d209) 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/60/33960/3 updated (fefc71ebc -> a1a679039)

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/60/33960/3 in repository toolchain/jenkins-scripts. discards fefc71ebc tcwg_bmk-build.sh: Require setting ci_project adds a1a679039 tcwg_bmk-build.sh: Require setting ci_project 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 (fefc71ebc) \ N -- N -- N refs/changes/60/33960/3 (a1a679039) 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/60/33960/2 updated (2582fa3c6 -> ca550cce1)

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/60/33960/2 in repository toolchain/jenkins-scripts. discards 2582fa3c6 tcwg_bmk-build.sh: Add compatibility for not setting ci_project adds ca550cce1 tcwg_bmk-build.sh: Add compatibility for not setting ci_project 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 (2582fa3c6) \ N -- N -- N refs/changes/60/33960/2 (ca550cce1) 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/60/33960/1 updated (6bc99d2bf -> c9dd7e518)

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/60/33960/1 in repository toolchain/jenkins-scripts. discards 6bc99d2bf tcwg_bmk-build.sh: Add compatibility for not setting ci_project adds c9dd7e518 tcwg_bmk-build.sh: Add compatibility for not setting ci_project 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 (6bc99d2bf) \ N -- N -- N refs/changes/60/33960/1 (c9dd7e518) 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/60/30860/1 updated (759bf5b1e -> b808502f9)

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/60/30860/1 in repository toolchain/jenkins-scripts. discards 759bf5b1e start-container-docker.sh, jenkins-helpers.sh: Add --ssh_info option adds b808502f9 start-container-docker.sh, jenkins-helpers.sh: Add --ssh_info option 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 (759bf5b1e) \ N -- N -- N refs/changes/60/30860/1 (b808502f9) 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/60/30460/1 updated (77e720276 -> 6d5b859c3)

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/60/30460/1 in repository toolchain/jenkins-scripts. discards 77e720276 tcwg_bmk-build.sh: Pass "--target TARGET" to Clang adds 6d5b859c3 tcwg_bmk-build.sh: Pass "--target TARGET" to Clang 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 (77e720276) \ N -- N -- N refs/changes/60/30460/1 (6d5b859c3) 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/60/30260/3 updated (ddddcf637 -> aeedd7d86)

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/60/30260/3 in repository toolchain/jenkins-scripts. discards ddddcf637 [rr-many 3/N] Rework trigger files for follow-up builds. adds aeedd7d86 [rr-many 3/N] Rework trigger files for follow-up 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 (ddddcf637) \ N -- N -- N refs/changes/60/30260/3 (aeedd7d86) 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/60/30260/2 updated (395891604 -> b15d40918)

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/60/30260/2 in repository toolchain/jenkins-scripts. discards 395891604 [rr-many 3/N] Rework trigger files for follow-up builds. adds b15d40918 [rr-many 3/N] Rework trigger files for follow-up 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 (395891604) \ N -- N -- N refs/changes/60/30260/2 (b15d40918) 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/60/30260/1 updated (d4084ea1e -> dc2d29758)

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/60/30260/1 in repository toolchain/jenkins-scripts. discards d4084ea1e [rr-many 3/N] Rework trigger files for follow-up builds. adds dc2d29758 [rr-many 3/N] Rework trigger files for follow-up 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 (d4084ea1e) \ N -- N -- N refs/changes/60/30260/1 (dc2d29758) 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/60/29960/2 updated (e9dc86fb7 -> 1edbdc4fc)

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/60/29960/2 in repository toolchain/jenkins-scripts. discards e9dc86fb7 tcwg_kernel/*: Remove unused configuration files. adds 1edbdc4fc tcwg_kernel/*: Remove unused configuration files. 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 (e9dc86fb7) \ N -- N -- N refs/changes/60/29960/2 (1edbdc4fc) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024