Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/00/31400/2 updated (8cb81a1db -> 36b70c76c)

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/00/31400/2 in repository toolchain/jenkins-scripts. discards 8cb81a1db jenkins-helpers.sh: print_arch_for_label() Add support for tc [...] adds 36b70c76c jenkins-helpers.sh: print_arch_for_label() Add support for tc [...] 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 (8cb81a1db) \ N -- N -- N refs/changes/00/31400/2 (36b70c76c) 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

[toolchain/jenkins-scripts] reference refs/changes/00/31400/1 updated (935002750 -> 4740f09ee)

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/00/31400/1 in repository toolchain/jenkins-scripts. discards 935002750 jenkins-helpers.sh: print_arch_for_label() Add support for tc [...] adds 4740f09ee jenkins-helpers.sh: print_arch_for_label() Add support for tc [...] 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 (935002750) \ N -- N -- N refs/changes/00/31400/1 (4740f09ee) 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

[toolchain/jenkins-scripts] reference refs/cache-automerge/b1/a1dd00d4dfd4df89f613ac64189b62b687a247 updated (931511e8a -> 51a8ea423)

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/cache-automerge/b1/a1dd00d4dfd4df89f613ac64189b62b687a247 in repository toolchain/jenkins-scripts. discards 931511e8a Auto-merge of b1a1dd00d4dfd4df89f613ac64189b62b687a247 new 51a8ea423 Auto-merge of b1a1dd00d4dfd4df89f613ac64189b62b687a247 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 (931511e8a) \ N -- N -- N refs/cache-automerge/b1/a1dd00d4dfd4df89f613ac64189b62b6 [...] 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

[toolchain/jenkins-scripts] reference refs/cache-automerge/76/a591e7ce31ac82b91cdae108af77d7efb5de8e updated (71e6544a9 -> 33ecc0812)

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/cache-automerge/76/a591e7ce31ac82b91cdae108af77d7efb5de8e in repository toolchain/jenkins-scripts. discards 71e6544a9 Auto-merge of 76a591e7ce31ac82b91cdae108af77d7efb5de8e new 33ecc0812 Auto-merge of 76a591e7ce31ac82b91cdae108af77d7efb5de8e 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 (71e6544a9) \ N -- N -- N refs/cache-automerge/76/a591e7ce31ac82b91cdae108af77d7ef [...] 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

[glibc] branch release/2.37/master updated (3da1b0064a -> 708f507e30)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.37/master in repository glibc. from 3da1b0064a resolv: Do not wait for non-existing second DNS response aft [...] new 708f507e30 resolv: Track single-request fallback via _res._flags (bug 31476) 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: NEWS | 1 + resolv/res_send.c | 12 +++++++----- resolv/resolv-internal.h | 2 ++ 3 files changed, 10 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 months

[toolchain/jenkins-scripts] reference refs/cache-automerge/70/6939dbdd7440698836cea210861cdd6e7e5f2a updated (9da2b1536 -> 935a59477)

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/cache-automerge/70/6939dbdd7440698836cea210861cdd6e7e5f2a in repository toolchain/jenkins-scripts. discards 9da2b1536 Auto-merge of 4071968556f2b2e33b363600224e3002aa00854d new 935a59477 Auto-merge of 4071968556f2b2e33b363600224e3002aa00854d 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 (9da2b1536) \ N -- N -- N refs/cache-automerge/70/6939dbdd7440698836cea210861cdd6e [...] 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

[glibc] branch release/2.36/master updated (789addc412 -> 3d252f17b8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.36/master in repository glibc. from 789addc412 resolv: Do not wait for non-existing second DNS response aft [...] new 3d252f17b8 resolv: Track single-request fallback via _res._flags (bug 31476) 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: NEWS | 1 + resolv/res_send.c | 12 +++++++----- resolv/resolv-internal.h | 2 ++ 3 files changed, 10 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

4 months

[toolchain/jenkins-scripts] reference refs/cache-automerge/6a/ae8cbdde8c01530ae71f1a5aa60e4fdf746b30 updated (70628e5e3 -> 16d733d72)

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/cache-automerge/6a/ae8cbdde8c01530ae71f1a5aa60e4fdf746b30 in repository toolchain/jenkins-scripts. discards 70628e5e3 Auto-merge of 6aae8cbdde8c01530ae71f1a5aa60e4fdf746b30 new 16d733d72 Auto-merge of 6aae8cbdde8c01530ae71f1a5aa60e4fdf746b30 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 (70628e5e3) \ N -- N -- N refs/cache-automerge/6a/ae8cbdde8c01530ae71f1a5aa60e4fdf [...] 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

[toolchain/jenkins-scripts] reference refs/cache-automerge/65/c08b0b1756e96995444037720ffde628094220 updated (79c27555e -> 154485aae)

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/cache-automerge/65/c08b0b1756e96995444037720ffde628094220 in repository toolchain/jenkins-scripts. discards 79c27555e Auto-merge of 65c08b0b1756e96995444037720ffde628094220 new 154485aae Auto-merge of 65c08b0b1756e96995444037720ffde628094220 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 (79c27555e) \ N -- N -- N refs/cache-automerge/65/c08b0b1756e96995444037720ffde628 [...] 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

[toolchain/jenkins-scripts] reference refs/cache-automerge/5a/0e2ea9b94e018d5566c6de85f4bd034bcbb22a updated (8ff2c82c5 -> e85d73352)

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/cache-automerge/5a/0e2ea9b94e018d5566c6de85f4bd034bcbb22a in repository toolchain/jenkins-scripts. discards 8ff2c82c5 Auto-merge of 5a0e2ea9b94e018d5566c6de85f4bd034bcbb22a new e85d73352 Auto-merge of 5a0e2ea9b94e018d5566c6de85f4bd034bcbb22a 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 (8ff2c82c5) \ N -- N -- N refs/cache-automerge/5a/0e2ea9b94e018d5566c6de85f4bd034b [...] 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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024