Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/69/44369/9 updated (4d7ef9738 -> 88dee9f7e)

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/69/44369/9 in repository toolchain/jenkins-scripts. discards 4d7ef9738 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] adds 88dee9f7e pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] 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 (4d7ef9738) \ N -- N -- N refs/changes/69/44369/9 (88dee9f7e) 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, 3 months

[toolchain/jenkins-scripts] reference refs/changes/69/44369/8 updated (c70180ee8 -> 9f9b93708)

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/69/44369/8 in repository toolchain/jenkins-scripts. discards c70180ee8 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] adds 9f9b93708 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] 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 (c70180ee8) \ N -- N -- N refs/changes/69/44369/8 (9f9b93708) 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, 3 months

[toolchain/jenkins-scripts] reference refs/changes/69/44369/7 updated (1c653f9f2 -> b335975ae)

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/69/44369/7 in repository toolchain/jenkins-scripts. discards 1c653f9f2 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] adds b335975ae pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] 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 (1c653f9f2) \ N -- N -- N refs/changes/69/44369/7 (b335975ae) 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, 3 months

[toolchain/jenkins-scripts] reference refs/changes/69/44369/6 updated (e8ed2092f -> 3910173d8)

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/69/44369/6 in repository toolchain/jenkins-scripts. discards e8ed2092f pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] adds 3910173d8 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] 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 (e8ed2092f) \ N -- N -- N refs/changes/69/44369/6 (3910173d8) 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, 3 months

[toolchain/jenkins-scripts] reference refs/changes/69/44369/5 updated (a07675915 -> 43501db49)

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/69/44369/5 in repository toolchain/jenkins-scripts. discards a07675915 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] adds 43501db49 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] 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 (a07675915) \ N -- N -- N refs/changes/69/44369/5 (43501db49) 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, 3 months

[toolchain/jenkins-scripts] reference refs/changes/69/44369/4 updated (6e01bd83a -> 4b4e787c3)

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/69/44369/4 in repository toolchain/jenkins-scripts. discards 6e01bd83a pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] adds 4b4e787c3 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] 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 (6e01bd83a) \ N -- N -- N refs/changes/69/44369/4 (4b4e787c3) 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, 3 months

[toolchain/jenkins-scripts] reference refs/changes/69/44369/3 updated (5e96f8070 -> 56e0392ef)

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/69/44369/3 in repository toolchain/jenkins-scripts. discards 5e96f8070 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] adds 56e0392ef pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] 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 (5e96f8070) \ N -- N -- N refs/changes/69/44369/3 (56e0392ef) 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, 3 months

[toolchain/jenkins-scripts] reference refs/changes/69/44369/2 updated (efbb62c45 -> bec4974c3)

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/69/44369/2 in repository toolchain/jenkins-scripts. discards efbb62c45 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] new bec4974c3 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] 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 (efbb62c45) \ N -- N -- N refs/changes/69/44369/2 (bec4974c3) 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, 3 months

[toolchain/jenkins-scripts] reference refs/changes/69/44369/14 updated (49e82466d -> 3b0c7dc32)

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/69/44369/14 in repository toolchain/jenkins-scripts. discards 49e82466d pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] adds 3b0c7dc32 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] 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 (49e82466d) \ N -- N -- N refs/changes/69/44369/14 (3b0c7dc32) 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, 3 months

[toolchain/jenkins-scripts] reference refs/changes/69/44369/13 updated (6d7dca8f4 -> 1e5885456)

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/69/44369/13 in repository toolchain/jenkins-scripts. discards 6d7dca8f4 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] adds 1e5885456 pw-{trigger,apply,report,helpers}.sh: New scripts for pre-com [...] 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 (6d7dca8f4) \ N -- N -- N refs/changes/69/44369/13 (1e5885456) 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, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024