Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/04/37004/2 updated (35f344aad -> 149125a1f)

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/04/37004/2 in repository toolchain/jenkins-scripts. discards 35f344aad tcwg-llvm-testsuite.sh: Remove use of llvm-reference and upda [...] adds 149125a1f tcwg-llvm-testsuite.sh: Remove use of llvm-reference and upda [...] 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 (35f344aad) \ N -- N -- N refs/changes/04/37004/2 (149125a1f) 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/04/37004/1 updated (049a129e2 -> a9d7e6fd0)

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/04/37004/1 in repository toolchain/jenkins-scripts. discards 049a129e2 tcwg-llvm-testsuite.sh: Remove use of llvm-reference and upda [...] new a9d7e6fd0 tcwg-llvm-testsuite.sh: Remove use of llvm-reference and upda [...] 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 (049a129e2) \ N -- N -- N refs/changes/04/37004/1 (a9d7e6fd0) 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/04/36704/3 updated (fd7682fdc -> 224536ddd)

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/04/36704/3 in repository toolchain/jenkins-scripts. discards fd7682fdc tcsg-llvm-common.sh: Don't prefix with public_html adds 224536ddd tcsg-llvm-common.sh: Don't prefix with public_html 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 (fd7682fdc) \ N -- N -- N refs/changes/04/36704/3 (224536ddd) 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/04/36704/2 updated (06288fb1a -> e6732b39c)

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/04/36704/2 in repository toolchain/jenkins-scripts. discards 06288fb1a tcsg-llvm-common.sh: Don't prefix with public_html new e6732b39c tcsg-llvm-common.sh: Don't prefix with public_html 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 (06288fb1a) \ N -- N -- N refs/changes/04/36704/2 (e6732b39c) 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/04/36704/1 updated (9d4a8b9be -> ee453eb57)

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/04/36704/1 in repository toolchain/jenkins-scripts. discards 9d4a8b9be tcsg-llvm-commin.sh: Don't prefix with public_html new ee453eb57 tcsg-llvm-commin.sh: Don't prefix with public_html 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 (9d4a8b9be) \ N -- N -- N refs/changes/04/36704/1 (ee453eb57) 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/04/30904/4 updated (4ecd3dc43 -> d20c44a72)

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/04/30904/4 in repository toolchain/jenkins-scripts. discards 4ecd3dc43 round-robin.sh: Add ${rr[update_baseline]} "rebase" capability adds d20c44a72 round-robin.sh: Add ${rr[update_baseline]} "rebase" capability 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 (4ecd3dc43) \ N -- N -- N refs/changes/04/30904/4 (d20c44a72) 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/04/30904/3 updated (4506ccb5d -> 9370b42bb)

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/04/30904/3 in repository toolchain/jenkins-scripts. discards 4506ccb5d round-robin.sh: Add ${rr[update_baseline]} "rebase" capability new 9370b42bb round-robin.sh: Add ${rr[update_baseline]} "rebase" capability 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 (4506ccb5d) \ N -- N -- N refs/changes/04/30904/3 (9370b42bb) 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/04/30904/2 updated (0efabe2f3 -> a79ea87e8)

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/04/30904/2 in repository toolchain/jenkins-scripts. discards 0efabe2f3 round-robin.sh: Add ${rr[update_baseline]} "rebase" capability new a79ea87e8 round-robin.sh: Add ${rr[update_baseline]} "rebase" capability 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 (0efabe2f3) \ N -- N -- N refs/changes/04/30904/2 (a79ea87e8) 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/04/30904/1 updated (5f110ebf7 -> b7adaa627)

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/04/30904/1 in repository toolchain/jenkins-scripts. discards 5f110ebf7 round-robin.sh: Add ${rr[update_baseline]} "rebase" capability new b7adaa627 round-robin.sh: Add ${rr[update_baseline]} "rebase" capability 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 (5f110ebf7) \ N -- N -- N refs/changes/04/30904/1 (b7adaa627) 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/04/30004/2 updated (3e41ff19d -> c96310238)

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/04/30004/2 in repository toolchain/jenkins-scripts. discards 3e41ff19d tcwg_bmk-build: Skip header line when parsing results adds c96310238 tcwg_bmk-build: Skip header line when parsing results 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 (3e41ff19d) \ N -- N -- N refs/changes/04/30004/2 (c96310238) 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024