Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/46/46946/2 updated (201ec3b05 -> 76b7e12eb)

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/46/46946/2 in repository toolchain/jenkins-scripts. discards 201ec3b05 jenkins-helpers.sh: Add get_baseline_git_if_exists function t [...] adds 76b7e12eb jenkins-helpers.sh: Add get_baseline_git_if_exists function t [...] 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 (201ec3b05) \ N -- N -- N refs/changes/46/46946/2 (76b7e12eb) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/46/46946/1 updated (c6d360fa5 -> 2fc33355d)

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/46/46946/1 in repository toolchain/jenkins-scripts. discards c6d360fa5 (WIP) jenkins-helpers.sh: Add get_baseline_git_if_exists func [...] adds 2fc33355d (WIP) jenkins-helpers.sh: Add get_baseline_git_if_exists func [...] 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 (c6d360fa5) \ N -- N -- N refs/changes/46/46946/1 (2fc33355d) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/46/46546/4 updated (6f28cf135 -> b15137441)

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/46/46546/4 in repository toolchain/jenkins-scripts. discards 6f28cf135 tcwg-lnt/*,tcwg-update-lnt-results.sh: Add ability to maintai [...] adds b15137441 tcwg-lnt/*,tcwg-update-lnt-results.sh: Add ability to maintai [...] 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 (6f28cf135) \ N -- N -- N refs/changes/46/46546/4 (b15137441) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/46/46546/3 updated (27756a0a5 -> 673521e39)

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/46/46546/3 in repository toolchain/jenkins-scripts. discards 27756a0a5 tcwg-lnt/*,tcwg-update-lnt-results.sh: Add ability to maintai [...] new 673521e39 tcwg-lnt/*,tcwg-update-lnt-results.sh: Add ability to maintai [...] 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 (27756a0a5) \ N -- N -- N refs/changes/46/46546/3 (673521e39) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/46/46546/2 updated (77392b1e1 -> ca435b564)

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/46/46546/2 in repository toolchain/jenkins-scripts. discards 77392b1e1 tcwg-lnt/*,tcwg-update-lnt-results.sh: Add ability to maintai [...] new ca435b564 tcwg-lnt/*,tcwg-update-lnt-results.sh: Add ability to maintai [...] 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 (77392b1e1) \ N -- N -- N refs/changes/46/46546/2 (ca435b564) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/46/46546/1 updated (c13b8e8d8 -> c02260e6e)

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/46/46546/1 in repository toolchain/jenkins-scripts. discards c13b8e8d8 tcwg-lnt: Add ability to create several servers new c02260e6e tcwg-lnt: Add ability to create several servers 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 (c13b8e8d8) \ N -- N -- N refs/changes/46/46546/1 (c02260e6e) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/46/46446/3 updated (c886cb6c7 -> 61bf90f64)

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/46/46446/3 in repository toolchain/jenkins-scripts. discards c886cb6c7 round-robin-notify.sh,lnt-utils.sh: Adjust run_order adds 61bf90f64 round-robin-notify.sh,lnt-utils.sh: Adjust run_order 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 (c886cb6c7) \ N -- N -- N refs/changes/46/46446/3 (61bf90f64) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/46/46446/2 updated (b802f8e2e -> 4a14a6c29)

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/46/46446/2 in repository toolchain/jenkins-scripts. discards b802f8e2e round-robin-notify.sh,lnt-utils.sh: Adjust run_order new 4a14a6c29 round-robin-notify.sh,lnt-utils.sh: Adjust run_order 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 (b802f8e2e) \ N -- N -- N refs/changes/46/46446/2 (4a14a6c29) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/46/46446/1 updated (6bd2978eb -> 54775a592)

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/46/46446/1 in repository toolchain/jenkins-scripts. discards 6bd2978eb round-robin-notify.sh,lnt-utils.sh: Adjust run_order new 54775a592 round-robin-notify.sh,lnt-utils.sh: Adjust run_order 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 (6bd2978eb) \ N -- N -- N refs/changes/46/46446/1 (54775a592) 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, 3 weeks

[toolchain/jenkins-scripts] reference refs/changes/46/46346/1 updated (c3f2bae99 -> 99815b931)

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/46/46346/1 in repository toolchain/jenkins-scripts. discards c3f2bae99 lnt-utils.sh: Disable some debug traces adds 99815b931 lnt-utils.sh: Disable some debug traces 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 (c3f2bae99) \ N -- N -- N refs/changes/46/46346/1 (99815b931) 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, 3 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024