Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/18/29618/1 updated (b4f95fc6e -> f64a6ae76)

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/18/29618/1 in repository toolchain/jenkins-scripts. discards b4f95fc6e jenkins-helpers.sh: Include contents of sourced config files [...] adds f64a6ae76 jenkins-helpers.sh: Include contents of sourced config 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 (b4f95fc6e) \ N -- N -- N refs/changes/18/29618/1 (f64a6ae76) 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/18/29018/4 updated (0aad119ad -> 1a5209829)

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/18/29018/4 in repository toolchain/jenkins-scripts. discards 0aad119ad tcwg_kernel-bisect.sh: New bisect script. adds 1a5209829 tcwg_kernel-bisect.sh: New bisect script. 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 (0aad119ad) \ N -- N -- N refs/changes/18/29018/4 (1a5209829) 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/18/29018/3 updated (3b5d6aa34 -> dd8196582)

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/18/29018/3 in repository toolchain/jenkins-scripts. discards 3b5d6aa34 tcwg_kernel-bisect.sh: New bisect script. new dd8196582 tcwg_kernel-bisect.sh: New bisect script. 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 (3b5d6aa34) \ N -- N -- N refs/changes/18/29018/3 (dd8196582) 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/18/29018/2 updated (1621c2d93 -> 90ed2c7ca)

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/18/29018/2 in repository toolchain/jenkins-scripts. discards 1621c2d93 tcwg_kernel-bisect.sh: New bisect script. new 90ed2c7ca tcwg_kernel-bisect.sh: New bisect script. 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 (1621c2d93) \ N -- N -- N refs/changes/18/29018/2 (90ed2c7ca) 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/18/29018/1 updated (447b98fec -> 43dfe470f)

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/18/29018/1 in repository toolchain/jenkins-scripts. discards 447b98fec tcwg_kernel-bisect.sh: New bisect script. new 43dfe470f tcwg_kernel-bisect.sh: New bisect script. 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 (447b98fec) \ N -- N -- N refs/changes/18/29018/1 (43dfe470f) 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/17/46317/6 updated (ffa51533d -> e53a9f940)

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/17/46317/6 in repository toolchain/jenkins-scripts. discards ffa51533d tcwg-lnt/patches: Add status for bmk schemas adds e53a9f940 tcwg-lnt/patches: Add status for bmk schemas 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 (ffa51533d) \ N -- N -- N refs/changes/17/46317/6 (e53a9f940) 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/17/46317/5 updated (b35bf27a3 -> 46ae2e26b)

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/17/46317/5 in repository toolchain/jenkins-scripts. discards b35bf27a3 tcwg-lnt/patches: Add status for bmk schemas adds 46ae2e26b tcwg-lnt/patches: Add status for bmk schemas 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 (b35bf27a3) \ N -- N -- N refs/changes/17/46317/5 (46ae2e26b) 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/17/46317/4 updated (4d0689ecb -> b575623eb)

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/17/46317/4 in repository toolchain/jenkins-scripts. discards 4d0689ecb tcwg-lnt/patches: Add status for bmk schemas adds b575623eb tcwg-lnt/patches: Add status for bmk schemas 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 (4d0689ecb) \ N -- N -- N refs/changes/17/46317/4 (b575623eb) 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/17/46317/3 updated (1273dd896 -> e7aa6f66b)

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/17/46317/3 in repository toolchain/jenkins-scripts. discards 1273dd896 tcwg-lnt/patches: Add status for bmk schemas new e7aa6f66b tcwg-lnt/patches: Add status for bmk schemas 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 (1273dd896) \ N -- N -- N refs/changes/17/46317/3 (e7aa6f66b) 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/17/46317/2 updated (a5e3140eb -> 2b61fa554)

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/17/46317/2 in repository toolchain/jenkins-scripts. discards a5e3140eb tcwg-lnt/patches: Add status for bmk schemas new 2b61fa554 tcwg-lnt/patches: Add status for bmk schemas 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 (a5e3140eb) \ N -- N -- N refs/changes/17/46317/2 (2b61fa554) 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