Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/29/44429/3 updated (7ca328708 -> 11750de36)

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/29/44429/3 in repository toolchain/jenkins-scripts. discards 7ca328708 tcwg_bmk-build.sh: Use output-bmk-results output for bmk adds 11750de36 tcwg_bmk-build.sh: Use output-bmk-results output for bmk 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 (7ca328708) \ N -- N -- N refs/changes/29/44429/3 (11750de36) 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/29/44429/2 updated (cfee830cf -> f5e037cf1)

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/29/44429/2 in repository toolchain/jenkins-scripts. discards cfee830cf tcwg_bmk-build.sh: Use output-bmk-results output for bmk adds f5e037cf1 tcwg_bmk-build.sh: Use output-bmk-results output for bmk 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 (cfee830cf) \ N -- N -- N refs/changes/29/44429/2 (f5e037cf1) 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/29/44429/1 updated (a2ac1c0b2 -> bf164a53f)

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/29/44429/1 in repository toolchain/jenkins-scripts. discards a2ac1c0b2 tcwg_bmk-build.sh: Use output-bmk-results output for bmk new bf164a53f tcwg_bmk-build.sh: Use output-bmk-results output for bmk 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 (a2ac1c0b2) \ N -- N -- N refs/changes/29/44429/1 (bf164a53f) 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/29/44329/8 updated (a533b9a1c -> c17633bf8)

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/29/44329/8 in repository toolchain/jenkins-scripts. discards a533b9a1c tcwg_gnu-build.sh: Rename tcwg_gnu_eabi_cross into tcwg_gnu_embed adds c17633bf8 tcwg_gnu-build.sh: Rename tcwg_gnu_eabi_cross into tcwg_gnu_embed 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 (a533b9a1c) \ N -- N -- N refs/changes/29/44329/8 (c17633bf8) 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/29/44329/7 updated (8b151e402 -> e53231967)

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/29/44329/7 in repository toolchain/jenkins-scripts. discards 8b151e402 tcwg_gnu-build.sh: Rename tcwg_gnu_eabi_cross into tcwg_gnu_embed new e53231967 tcwg_gnu-build.sh: Rename tcwg_gnu_eabi_cross into tcwg_gnu_embed 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 (8b151e402) \ N -- N -- N refs/changes/29/44329/7 (e53231967) 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/29/44329/6 updated (d1deae09a -> 847150680)

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/29/44329/6 in repository toolchain/jenkins-scripts. discards d1deae09a tcwg_gnu-build.sh: Rename tcwg_gnu_eabi_cross into tcwg_gnu_embed adds 847150680 tcwg_gnu-build.sh: Rename tcwg_gnu_eabi_cross into tcwg_gnu_embed 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 (d1deae09a) \ N -- N -- N refs/changes/29/44329/6 (847150680) 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/29/44329/5 updated (ab0b9b51d -> d48412775)

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/29/44329/5 in repository toolchain/jenkins-scripts. discards ab0b9b51d tcwg_gnu-build.sh: Rename tcwg_gnu_eabi_cross into tcwg_gnu_embed new d48412775 tcwg_gnu-build.sh: Rename tcwg_gnu_eabi_cross into tcwg_gnu_embed 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 (ab0b9b51d) \ N -- N -- N refs/changes/29/44329/5 (d48412775) 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/29/44329/4 updated (e9bbc3bc6 -> 393fe738d)

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/29/44329/4 in repository toolchain/jenkins-scripts. discards e9bbc3bc6 tcwg_gnu-build.sh: Rename tcwg_gnu_eabi_cross into tcwg_gnu_embed new 393fe738d tcwg_gnu-build.sh: Rename tcwg_gnu_eabi_cross into tcwg_gnu_embed 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 (e9bbc3bc6) \ N -- N -- N refs/changes/29/44329/4 (393fe738d) 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/29/44329/3 updated (47832d206 -> 9d0bcbcc5)

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/29/44329/3 in repository toolchain/jenkins-scripts. discards 47832d206 tcwg_gnu-build.sh: Rename tcwg_gnu_eabi* into tcwg_gnu_embed* new 9d0bcbcc5 tcwg_gnu-build.sh: Rename tcwg_gnu_eabi* into tcwg_gnu_embed* 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 (47832d206) \ N -- N -- N refs/changes/29/44329/3 (9d0bcbcc5) 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/29/44329/2 updated (f9e594c03 -> 66f7b8ab1)

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/29/44329/2 in repository toolchain/jenkins-scripts. discards f9e594c03 tcwg_gnu-build.sh: Rename tcwg_gnu_eabi* into tcwg_gnu_embed* adds 66f7b8ab1 tcwg_gnu-build.sh: Rename tcwg_gnu_eabi* into tcwg_gnu_embed* 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 (f9e594c03) \ N -- N -- N refs/changes/29/44329/2 (66f7b8ab1) 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