Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/06/47106/4 updated (42e66156b -> 639fd7442)

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/06/47106/4 in repository toolchain/jenkins-scripts. discards 42e66156b tcwg-update-lnt-results.sh: Move data to $lntimport/ directory adds 639fd7442 tcwg-update-lnt-results.sh: Move data to $lntimport/ directory 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 (42e66156b) \ N -- N -- N refs/changes/06/47106/4 (639fd7442) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/06/47106/3 updated (8e0d2df3f -> 0374acae4)

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/06/47106/3 in repository toolchain/jenkins-scripts. discards 8e0d2df3f tcwg-update-lnt-results.sh: Move data to $lntimport/ directory adds 0374acae4 tcwg-update-lnt-results.sh: Move data to $lntimport/ directory 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 (8e0d2df3f) \ N -- N -- N refs/changes/06/47106/3 (0374acae4) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/06/47106/2 updated (628c511a5 -> 8a5c4a6b1)

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/06/47106/2 in repository toolchain/jenkins-scripts. discards 628c511a5 tcwg-update-lnt-results.sh: Move data to $lntimport/ directory adds 8a5c4a6b1 tcwg-update-lnt-results.sh: Move data to $lntimport/ directory 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 (628c511a5) \ N -- N -- N refs/changes/06/47106/2 (8a5c4a6b1) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/06/47106/1 updated (4923eb794 -> 09ed1311f)

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/06/47106/1 in repository toolchain/jenkins-scripts. discards 4923eb794 tcwg-update-lnt-results.sh: Move data to $lntimport/ directory adds 09ed1311f tcwg-update-lnt-results.sh: Move data to $lntimport/ directory 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 (4923eb794) \ N -- N -- N refs/changes/06/47106/1 (09ed1311f) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/06/46906/1 updated (65e4e6868 -> f1e1e0c4a)

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/06/46906/1 in repository toolchain/jenkins-scripts. discards 65e4e6868 tcwg_chromium-build.sh: Try fix to avoid apt-install interaction adds f1e1e0c4a tcwg_chromium-build.sh: Try fix to avoid apt-install interaction 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 (65e4e6868) \ N -- N -- N refs/changes/06/46906/1 (f1e1e0c4a) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/06/46806/5 updated (56c1b1628 -> a1d7ed346)

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/06/46806/5 in repository toolchain/jenkins-scripts. discards 56c1b1628 pw-apply.sh: Try to apply patches with -p1 then with -p0 adds a1d7ed346 pw-apply.sh: Try to apply patches with -p1 then with -p0 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 (56c1b1628) \ N -- N -- N refs/changes/06/46806/5 (a1d7ed346) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/06/46806/4 updated (56a5f04e0 -> 35bc4a587)

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/06/46806/4 in repository toolchain/jenkins-scripts. discards 56a5f04e0 pw-apply.sh: Try to apply patches with -p1 then with -p0 adds 35bc4a587 pw-apply.sh: Try to apply patches with -p1 then with -p0 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 (56a5f04e0) \ N -- N -- N refs/changes/06/46806/4 (35bc4a587) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/06/46806/3 updated (8ffb92e9a -> 431bdc1a9)

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/06/46806/3 in repository toolchain/jenkins-scripts. discards 8ffb92e9a pw-apply.sh: Try to apply patches with -p1 then with -p0 new 431bdc1a9 pw-apply.sh: Try to apply patches with -p1 then with -p0 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 (8ffb92e9a) \ N -- N -- N refs/changes/06/46806/3 (431bdc1a9) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/06/46806/2 updated (9b8919b85 -> bc3760ec8)

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/06/46806/2 in repository toolchain/jenkins-scripts. discards 9b8919b85 pw-apply.sh: Try to apply patches with -p1 then with -p0 new bc3760ec8 pw-apply.sh: Try to apply patches with -p1 then with -p0 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 (9b8919b85) \ N -- N -- N refs/changes/06/46806/2 (bc3760ec8) 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.

4 months, 1 week

[toolchain/jenkins-scripts] reference refs/changes/06/46806/1 updated (066a1d3bc -> 1361a85c4)

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/06/46806/1 in repository toolchain/jenkins-scripts. discards 066a1d3bc pw-apply.sh: Try to apply patches with -p1 then with -p0 new 1361a85c4 pw-apply.sh: Try to apply patches with -p1 then with -p0 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 (066a1d3bc) \ N -- N -- N refs/changes/06/46806/1 (1361a85c4) 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.

4 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024