Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/56/44156/3 updated (b3da21731 -> 25d231d27)

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/56/44156/3 in repository toolchain/jenkins-scripts. discards b3da21731 shadow-ar.sh: remove useless error cases of missing orig_out adds 25d231d27 shadow-ar.sh: remove useless error cases of missing orig_out 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 (b3da21731) \ N -- N -- N refs/changes/56/44156/3 (25d231d27) 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, 5 months

[toolchain/jenkins-scripts] reference refs/changes/56/44156/2 updated (fc24094a6 -> 9f5c3ec17)

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/56/44156/2 in repository toolchain/jenkins-scripts. discards fc24094a6 shadow-ar.sh: remove useless error cases of missing orig_out new 9f5c3ec17 shadow-ar.sh: remove useless error cases of missing orig_out 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 (fc24094a6) \ N -- N -- N refs/changes/56/44156/2 (9f5c3ec17) 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.

1 year, 5 months

[toolchain/jenkins-scripts] reference refs/changes/56/44156/1 updated (be1430726 -> 112a3c3ce)

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/56/44156/1 in repository toolchain/jenkins-scripts. discards be1430726 shadow-ar.sh: remove useless error cases of missing orig_out new 112a3c3ce shadow-ar.sh: remove useless error cases of missing orig_out 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 (be1430726) \ N -- N -- N refs/changes/56/44156/1 (112a3c3ce) 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.

1 year, 5 months

[toolchain/jenkins-scripts] reference refs/changes/56/43556/3 updated (033667845 -> 4cdbb4059)

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/56/43556/3 in repository toolchain/jenkins-scripts. discards 033667845 round-robin.sh,round-robin-notify.sh: Generate mail at notify stage adds 4cdbb4059 round-robin.sh,round-robin-notify.sh: Generate mail at notify stage 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 (033667845) \ N -- N -- N refs/changes/56/43556/3 (4cdbb4059) 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, 5 months

[toolchain/jenkins-scripts] reference refs/changes/56/43556/2 updated (e1a129538 -> cab209a21)

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/56/43556/2 in repository toolchain/jenkins-scripts. discards e1a129538 round-robin.sh,round-robin-notify.sh: Generate mail at notify stage new cab209a21 round-robin.sh,round-robin-notify.sh: Generate mail at notify stage 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 (e1a129538) \ N -- N -- N refs/changes/56/43556/2 (cab209a21) 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.

1 year, 5 months

[toolchain/jenkins-scripts] reference refs/changes/56/43556/1 updated (33462d1b6 -> 05caed445)

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/56/43556/1 in repository toolchain/jenkins-scripts. discards 33462d1b6 round-robin.sh,round-robin-notify.sh: Generate mail at notify stage new 05caed445 round-robin.sh,round-robin-notify.sh: Generate mail at notify stage 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 (33462d1b6) \ N -- N -- N refs/changes/56/43556/1 (05caed445) 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.

1 year, 5 months

[toolchain/jenkins-scripts] reference refs/changes/56/42756/4 updated (d27c25072 -> 3e10da1de)

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/56/42756/4 in repository toolchain/jenkins-scripts. discards d27c25072 jenkins-herlpers.sh: fresh_dir also handle directories with n [...] adds 3e10da1de jenkins-herlpers.sh: fresh_dir also handle directories with n [...] 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 (d27c25072) \ N -- N -- N refs/changes/56/42756/4 (3e10da1de) 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, 5 months

[toolchain/jenkins-scripts] reference refs/changes/56/42756/3 updated (8d885f510 -> d30ee4fb1)

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/56/42756/3 in repository toolchain/jenkins-scripts. discards 8d885f510 jenkins-herlpers.sh: fresh_dir also handle directories with n [...] new d30ee4fb1 jenkins-herlpers.sh: fresh_dir also handle directories with n [...] 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 (8d885f510) \ N -- N -- N refs/changes/56/42756/3 (d30ee4fb1) 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.

1 year, 5 months

[toolchain/jenkins-scripts] reference refs/changes/56/42756/2 updated (97af10666 -> 9eea551de)

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/56/42756/2 in repository toolchain/jenkins-scripts. discards 97af10666 jenkins-herlpers.sh: fresh_dir also handle directories with n [...] new 9eea551de jenkins-herlpers.sh: fresh_dir also handle directories with n [...] 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 (97af10666) \ N -- N -- N refs/changes/56/42756/2 (9eea551de) 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.

1 year, 5 months

[toolchain/jenkins-scripts] reference refs/changes/56/42756/1 updated (021c4c31a -> 809ce6792)

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/56/42756/1 in repository toolchain/jenkins-scripts. discards 021c4c31a round-robin.sh: Workaround for gcc bugz #107940 new 809ce6792 round-robin.sh: Workaround for gcc bugz #107940 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 (021c4c31a) \ N -- N -- N refs/changes/56/42756/1 (809ce6792) 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.

1 year, 5 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024